@masnick.com I’m listening to your interview with @reckless.bsky.social. This third party doctrine is interesting. Do you think that atproto data would be considered properly owned by the account individual? Would be interesting implications if that public data fall under search and seizure rights.

NEW BLOG! After closely following atproto permissioned data, my take: what if an "atproto repository" is the base thing and there's more than one way to sync it? Based on @ipv.sx's take and grounded in a real-world Streamplace use case: how do I make a video private, then public?

So is data stored in public right now and will become private once the specs land, or is data just not stored on ATproto and will be migrated once the specs land?

Random musings: I think I kinda understand where attie, or a tool like it, exists now. This is a long play that will only reach its final state if access to data important to a user continues to improve within atproto. The model performance is irrelevant. It's just a data problem.

continuing to build up our permissioned data protocol! this one asks what a bucket actually is and where the data that constitutes a bucket is stored. it argues for maintaining the atproto ethos in the permissioned data protocol as always, looking forward to hearing your thoughts!