GrapheneOS security preview releases

GrapheneOS

pixel9538 We haven't figured it out yet because the whole patch system is such a mess. Patches frequently get deferred to a future security bulletin or replaced. It's very hard to keep track of what happened with everything and when everything has been disclosed in the bulletins if at all.

lip

userofgos why grapheneOS still rely on X for informing its users when we have nostr which is the only troe foss social media?

Cellobright

lip Because they already have a self-hosted Mastodon instance and if they choose another messaging protocol like Nostr (which is not "the only true foss social media"; it is not the only one, and Notes and Other Stuff Transmitted by Relays is not a social media, the name tells it) they will be spending less time on useful development and more time uselessly managing accounts on too many platforms.

Carrousel7956

They do have a Nostr iirc.

Cellobright

Carrousel7956 Nostr and ActivityPub are not social media platforms; Mastodon, Bluesky, and Damus is. Check contact (grapheneos.org) for a list of all platforms they officially appear on.

The security@grapheneos.org address is for reporting high priority security issues related to GrapheneOS. [...] a much lower priority if you misuse this address.

The official X account for the project is @GrapheneOS which is used for official announcements.

The official Mastodon account for the project is @GrapheneOS@grapheneos.social which is used for official announcements.

The official Bluesky account for the project is @grapheneos.org which is used for official announcements.

Hiring [...]

No mention of a Nostr public key, indicating any "GrapheneOS" user on Nostr protocol is a mirror at best.

« Previous Page