one fundamental issue in atproto is the missing permissions layer, the proposal is insufficient for many use cases, graze was shut out of their main financial path by Bluesky (paid creator posts, Bluesky cut off talks)
tl;dr - people want control and privacy, not an open anonymous read all the data in the world, foundation for their online social activities, and this needs to be core to a protocol
I've also been holding off from jumping into building on AT proto for exactly that "no one wants all their data to be as public as possible" reason, but private data is now in alpha which is a meaningful step towards solving that: https://atproto.com/blog/atproto-spaces-alpha
Comments
one fundamental issue in atproto is the missing permissions layer, the proposal is insufficient for many use cases, graze was shut out of their main financial path by Bluesky (paid creator posts, Bluesky cut off talks)
tl;dr - people want control and privacy, not an open anonymous read all the data in the world, foundation for their online social activities, and this needs to be core to a protocol
I've also been holding off from jumping into building on AT proto for exactly that "no one wants all their data to be as public as possible" reason, but private data is now in alpha which is a meaningful step towards solving that: https://atproto.com/blog/atproto-spaces-alpha
its not a meaningful step, its a bare minimum (ACL) token acceptence of reality, I don't get the sense they actually believe in private data on social
its designed in such a minimal way that the app devs will have to implement on top for their features and create a centralization point
this is why I believe it needs to be baked into the core, part of the vision and ethos from the start