I think it’s because we use sensible languages that don’t c…

Samuel 8 May 2024

ok a few people have asked and I never answered because I knew I'd get a million quote posts (sorry), but here's the official stance on E2EE DMs tl;dr: 100% planned, but not right now in order to get the basic feature out there asap :)

Basic "Off-Protocol" Direct Messages (DMs): having some mechanism to privately contact other Bluesky accounts is the most requested product feature. We looked closely at alternatives like linking to external services, re-using an existing protocol like Matrix, or rushing out on-protocol encrypted DMs, but ultimately decided to launch a basic centralized system to take the time pressure off our team and make our user community happy. We intend to iterate and fully support E2EE DMs as part of atproto itself, without a centralized service, and will take the time to get the user experience, security, and privacy polished. This will be a distinct part of the protocol from the repository abstraction, which is only used for public content.

bryan newbold@bnewbold.net· 7 May 2024

atproto devs! got a new 2024 atproto roadmap posted. curious for your questions!

2024 Protocol Roadmap | Bluesky

Discuss this post in our Github Discussion forums here

docs.bsky.app

8 33 114

Samuel 8 May 2024

nice thing about this way around from the perspective of us appers is that we'll have already done the UI stuff, so E2EE will be easy peasy. cant say the same for the backend bois though lmao

3 1 37

David Buchanan 8 May 2024

yeah e2ee is easy on the backend you just gotta set the "is_encrypted" flag to True

4 1 30

hailey 8 May 2024

tried to explain that but there was some blocker idk

1 10

Samuel

@samuel.fm

I think it’s because we use sensible languages that don’t capitalize their booleans