Egregoros

@silverpill @phnt@fluffytail.org @feld@friedcheese.us

Fun fact: both E2EE clients in development right now support the “content” field in likes.

I was just demoing emoji reactions this morning.

We’re going to try to include it as a MAY or SHOULD in the spec, with fallbacks for regular Likes.

Have you seen this news?

#Mastodon just got funding to add end to end encryption into their software.

So, some time next year, you’ll be able to send truly private messages to the vast majority of the #Fediverse

Im so excited about this.

Because it’s an open spec, this opens the doors for every Fediverse app to join the party.

Yesterday, this project was a proof of concept. Today, Mastodon has turned it into a stampede.

#E2EE

https://blog.joinmastodon.org/2026/04/sovereign-tech-agency-funding/

Whenever they write the Wikipedia article about E2EE, I just want a footnote in there...

#Mastodon was the artillery, the big guns that made the difference. #Bonfire and #Emissary were the special forces recon teams that made it possible.

@silverpill @mariusor @trwnh

I *love* this idea - especially in principle. I say that because I’m having a hard time wrapping my head around this and how it would be used in practice.

Do you think you could post an example workflow (or three) to demonstrate how this would work?

I get that objects could be added to client-defined collections (very cool) but if object/collection IDs don’t have predefined semantics, how will I know where to look to get the data I need?