Mastodawn

Dear @volla, @murena, and whoever else is behind the Unified Attestation initiative - why can't you support pinning-based attestation instead of your anti-competitive stance? Oh wait... I already answered my own question. Shame on you for claiming "freedom" in your marketing. You are definitely not about our freedom!

More context and more details in this thread: https://grapheneos.social/@GrapheneOS/116287040736213258

GrapheneOS (@[email protected])

If apps are required to verify the hardware, operating system and their app for regulatory reasons they should use an approach supporting arbitrary roots of trust and operating systems. Android already has a standard hardware attestation system usable for this. Android's documentation and sample libraries are biased towards Google by using them as the only valid root of trust and the API is biased towards stock operating systems but it's better than a centralized API. https://infosec.exchange/@rene_mobile/116286110700616525

GrapheneOS Mastodon

Show thread

friend 🤖1d ago

@murena You are one of the parties behind the Unified Attestation initiative, correct? There is no freedom with you.

Show thread

friend 🤖Feb 10

@cyb_detective if you have not seen it already you might be interested in https://jmail.world too. Incredible interface.

Jmail, logged in as [email protected]

You are logged into [email protected], Jeffrey Epstein's email. Sourced from the November 2025 House Oversight Committee data release.

Jmail

Show thread

friend 🤖Jan 31

@GossiTheDog "the ratio of my ████████ might make ████████ unconfortable"

Show thread

friend 🤖Jan 28

@Tutanota You have to either call it apps or networks/protocols, but the current information is incorrect. "Matrix" is not an app, but the network/protocol. "Element" is one client for it (like e.g. Cinny or the Element based Schildi). Either way you have to merge Element + Matrix.

Show thread

friend 🤖Jan 27

@JadedBlueEyes

Thank you for bringing your attention to this matter.

This #slopshard

Show thread

friend 🤖Jan 26

@x I think I somehow borked my reply where I tried to reply to two handles at once https://infosec.exchange/@fsoc/115964099552701196

Show thread

friend 🤖Jan 26

@jordisalvia @[email protected]

Really appreciate your replies. Sorry for this confusing post.

Felt really isolated in my self-hosting journey tonight. Spend a lot of time tinkering and just can't talk to anybody at home about the tech things that excite me. Wanted to reach out to the fediverse to get any interaction at all. So thank you for pulling me out of my one-person bubble just now!

When daydreaming I see a big community that uses my self-hosted services at fsoc.lol. People that have similar interests and exchange their experiences with self-hosting foss services. In reality I'm the the lone user of the apps I'm hosting - except a few local homelab services for family. That's the honest primary motivation of that post.

As it turns out I got to learn a few additional things. I'm in the process of figuring out the intricacies of Mastodon integration with Wordpress. Sent the post from my website as Fediverse participant. It's now pretty clear that I'm gonna primarily use my infosec.exchange account for the fediverse and limit @site to website / service update... for my imaginary community. Also saw how taxing the fediverse integration is for the tiny webserver and how to limit resources in my docker compose setup.

Thank you for your attention to this matter 😅

Show thread

friend 🤖Jan 26

@mrclark @site It all started with web clients for decentralized services: Phanpy for Mastodon, Photon for Lemmy, Element for Matrix.

Quickly spiraled into all kinds of web services and a few web apps I built myself.

Was especially interested in setting all up using docker compose with traefik & authentik. Just in awe what's available nowadays (fellow grump old guy)

friend 🤖Jan 26

RE: https://fsoc.lol/2026/01/26/looking-for-self-hosting-companions/

Still figuring out the best way to interact with the #fediverse. I think at the moment and the way #mastodon integrates with #wordpress it's best to primarily use the infosec.exchange account and limit @site to community / website updates.

Anybody else on their #selfhosting journey? Or interested in following along?