Big milestone!
✅ Federated domain handles
✅ Federated feed generators (algorithms)
✅ Federated relays (event firehose)
✅ Federated app views (API service)
✅ Federated data for self-hosters (PDS hosting)
✅ Federated moderation (labeling)
🚧 Federated data for large service providers (coming soon)
✅ Federated domain handles
✅ Federated feed generators (algorithms)
✅ Federated relays (event firehose)
✅ Federated app views (API service)
✅ Federated data for self-hosters (PDS hosting)
✅ Federated moderation (labeling)
🚧 Federated data for large service providers (coming soon)
Reposted from
AT Protocol Developers
Moderation is a crucial aspect of social networks. However, traditional moderation systems leave communities vulnerable to sudden policy changes and mismanagement.
To build a better social media ecosystem, it's necessary to try new approaches.
docs.bsky.app/blog/bluesky...
To build a better social media ecosystem, it's necessary to try new approaches.
docs.bsky.app/blog/bluesky...
Comments
Only your PDS host (in most cases, Bluesky Social, PBC) has private data and there's not much of it (email, mutes, subscribed labelers and not much else).
An internet user name, such as a name used to post to an online discussion forum.
Any social networking data, such as a person’s friend list and login information.
as personal info.
It's when you can't stop posting files onto the internet, a particularly nasty subset of poster's madness.
https://docs.ipfs.tech/
in general it's tough to justify unless you've got your own application (which I'm hoping we'll see more of now that the federated features are approaching a more stable state?) or you've got cash to throw away towards decentralization
Think it means pretty much the same thing in both cases. A collection of self determining parties that form a greater whole.
Makes labellers app-local, doesn't it?
https://bsky.app/profile/atproto.com/post/3knqrtlsgy22r
Actually the Relay doesn't consume labels from Labelers, it's on AppViews to do that, at least now (and maybe always).
The reason is that labels are not repo data on a PDS but a separate kind of data entirely.
My labels/likes to your posts live in my PDS, and get broadcasted, where AppView picks them and indexes/layers them on the target posts.
Then clients query AppView to see those same label/like records projected over the original records.
So likes are persistent and remain in PDS and have their footprint in CBOR file you can download.
But labels are just in a moment, right? Lucky if you saw them at the time of issuance, but if you've missed there is no going back. Is it?