proposals

I imagine the ATProto infrastructure would survive. Declining activity would be bad for BlueSky, but running a firehose is not that expensive. Many people could fund it themselves. Also, it would get cheaper to run as traffic declines. Also, the firehose is not strictly necessary either if you’re willing to give up seeing replies from anyone, anywhere and just see the feeds you subscribe to, like an RSS reader. The hard part is moderation and keeping up with changes in regulations, not the infrastructure itself. Also, continued funding for new development is good. I’m interested in seeing what the permissioned data proposal [1] turns into. [1] https://github.com/bluesky-social/proposals/tree/main/0016-p...

atproto permissioned data [1] will solve the dilemma you're describing. Ultimately all the data is in the same place (your PDS) and you can always read and write any data there. If startup A goes away, startup B can read that old data and do something useful with it. [1] https://github.com/bluesky-social/proposals/blob/main/0016-p...

There's a new feature being added to AT to support "permissioned data" that would handle a Slack-like use-case: https://github.com/bluesky-social/proposals/tree/main/0016-p...

Yes, AT proto is about making data available to the public via replication. There's no privacy at all, but it's useful for some things. Hacker News comments don't have any privacy either. There's another protocol in the works that should be useful for syncing private data: https://github.com/bluesky-social/proposals/pull/94

Rendered Markdown: https://github.com/bluesky-social/proposals/blob/permissione... Note this is an early draft and will likely change, as PR description says.

Bluesky / ATProto has a proposal for User Intents for data. More semantics than robots.txt, but equally unenforceable. Usage with AI is one of the intents to be signaled by users https://github.com/bluesky-social/proposals/tree/main/0008-u...

Check out the User Intent proposal, it's kind of like robots.txt, not enforceable, but also richer in semantics https://github.com/bluesky-social/proposals/tree/main/0008-u...

It’s driven by the PDSes and will be moving to this OAuth system soon: https://github.com/bluesky-social/proposals/blob/main/0004-o...

Users choose which 3p labelers they subscribe to. If a labeler service starts abusing their position, users can drop it. https://github.com/bluesky-social/proposals/tree/main/0002-l... is a deep-dive on how Bluesky sees labelers fitting into the ecosystem.