I agree that is borderline negligence, and by far the biggest issue with AT and Bsky. Here is what I believe to be the most recent discussion on that topic:

https://github.com/bluesky-social/atproto/discussions/3363

▲

quasigod a day ago | parent | next [-]

Theres more recent updates on it in a blog post from Bluesky head of protocol: https://dholms.leaflet.pub/3mhj6bcqats2o

	▲	consumer451 a day ago \| parent [-]
		Very cool! Thanks for sharing that.

▲

theturtletalks 2 days ago | parent | prev | next [-]

Having something like circles from the Google+ days would be needed if ATProto is going to go anywhere. Is it possible in the protocol?

	▲	Multicomp a day ago \| parent [-]
		Yeah having the messages be e2ee by default and then extending it out to one or more groups depending in which circles are currently included for messages could let atproto act like an encrypted group chat with crisscrossing group chats per message, which can ratchet up and along with the new enceyption keys each message/batch of 10 messages/hour/day until that client is dropped from a group or a group is dropped from a conversation, then the keys change and pfs prevents old clients from continuing to read future messages. Sure you can see that users emit messages in the pds but you dint know if its for your former group or other activitt

▲

verdverm a day ago | parent | prev [-]

The current conversations are around how to do permissined data properly on atproto. I have a prototype, but Bluesky hasn't participated in the community effort and looks to be doing their own thing. They also took Bain Capital "funding" (private equity) which was the breaking point for me. They could have set up subs for nothing and made more than that, hard fumble imo.