i wonder if diagrams like these might help draw the distinction between ActivityPub (and how Mastodon uses it) and AT Protocol (and how it’s used by Bluesky and atproto apps)?
with AP, instance = application + hosting. data gets sent between instances.
with AT, data flows *from* hosting *to* apps
AP’s credible exit: you can make a new twitter. however your data is stuck on the old one
AT’s credible exit: the data layer is independent from the apps and the network state is reproducible, so you can move to a new twitter seemlessly and even with an adversarial data host
bluesky is a “view” of all bluesky-type data on the open web. making a new “instance” of bluesky is to create a new “view” of the same data. this is like how Google and Bing have created independent search indexes of the same data
@samuel.bsky.team Slight modification needed though:
IndieWeb is Twitter but pulling data from the open web (microformats in html pages served over http)
Bluesky is the same but pulling data from the decentralized web (borrowing from eg IPFS)
@samuel.bsky.team My comment was only in relation to your “of all bluesky-type data on the open web”
The Bluesky data isn’t identified by http-url:s like content on the web is, but is identified by did:s and cid:s?
Aggregation is needed no matter if it’s Bluesky data or web data, so not a […]
dan@danabra.mov· 30 Oct 2024
