I just discovered the Fediverse (English) Wikipedia page has a huge section on AT Protocol and I question why. It seems like excessive promotion of Bluesky and its protocol that is not compatible with ActivityPub, both technically and in spirit. Illustrating bridging isn't the same as compatibility. Might as well add sections for other random network protocols like XMPP (Jabber).
Timeline
Post
Remote status
Context
1
@puppethead
Also the guy that wrote most of the AT protocol stuff in that article has this on his user page: https://en.wikipedia.org/wiki/User:Bocanegris#Wikipedia_will_be_AI-first
Clearer wording to emphasise that ActivityPub is not the entirety of the Fediverse- This statement is sometimes heavily disputed
Also the guy that wrote most of the AT protocol stuff in that article has this on his user page: https://en.wikipedia.org/wiki/User:Bocanegris#Wikipedia_will_be_AI-first
Replies
5@phnt@fluffytail.org @puppethead@ieji.de Surely written by a paid Bluesky shill. The Bluesky advertising should be removed from the Fediverse page.
[CW]
Content warning
somewhat adjacent in topic
Show
Hide
Content warning
somewhat adjacent in topic
@allison @phnt @puppethead the alternatives basically don't solve those problems either.
activitypub has effectively failed to even exist and is the mastodon protocol with occasional extensions
atproto doesn't solve mass distribution it just gives you a neotwitter API and says trust our relay bro
matrix doesn't solve mass distribution its a single company hosting most of the network on versions of the software they don't release
psyc actually did try (dedicated fanout and multicasting), as does nostr (negentropy is quite efficient)
activitypub has effectively failed to even exist and is the mastodon protocol with occasional extensions
atproto doesn't solve mass distribution it just gives you a neotwitter API and says trust our relay bro
matrix doesn't solve mass distribution its a single company hosting most of the network on versions of the software they don't release
psyc actually did try (dedicated fanout and multicasting), as does nostr (negentropy is quite efficient)