has there ever been confirmation that locked Bluesky accounts will arrive once atproto has implemented Privately Shared Data? people seem to assume product will follow protocol on this (and maybe it does!) but I can't recall seeing anything explicit docs.bsky.app/blog/2025-pr...

no, afaik there is no expectation of "locked accounts" in the traditional sense because the distribution model is very different for non-public posts. what probably can be done is a different type of post (decided at posting time, not switched back and forth per-account)

Yeah, that's what I was thinking too… a lot of people might be disappointed when this is done

I mean, does any decentralized/federated thing support Twitter-style private accounts? It doesn’t seem possible without a lot of really annoying cruft.

thanks, yeah, that makes sense

Distribution is one of the more interesting (unsolved?) aspects of private data. I've been pondering something akin to a PDS inbox, perhaps also with permission semantics How do we build feeds and notifications while keeping the good UX @atproto.com enables for public data? How about moderation?

Depends on how you define "switched back and forth" I could see a workflow where the content is moved, but may lose likes or similar. This would be close to copy-delete semantics or one could replace the prior with a ref to the new. Or dups, which is likely how content will show up in >1 namespace

thought it was said twitter-style locked accounts will NOT arrive her

Ah…

good info in here, hadn't seen this before

@bnewbold.net's comment therein has been guiding my efforts of private groups and content. Had a great IRL conversation about it since too!

This is also somewhat related, but specifically for block relationships: github.com/bluesky-soci.... I am hoping that it does get implemented sooner rather than later.

As I understand it, I think private blocks are much less likely than private posts/accounts

It's been discussed but the plans aren't set yet from what I can tell from the outside The biggest issue in a protocol like this is how to switch content from public to private and back and how that affects mirrors and more.