Former CEO of Twitter wanted to build a social protocol no-one can control, like SMTP or HTTP for social media. Bluesky’s ATProto was supposed to be an open source protocol that Twitter could eventually utilize, but then Musk happened and Bluesky started taking it to the wrong direction and everything fell apart in Dorsey’s mind.
A very revealing interview. I now see even more future in W3C’s ActivityPub.
I must wonder… if Dorsey truly wants to build something open, non-commercial and decentralized, why doesn’t he even look at the ActivityPub? Why not help it thrive? What’s all that fuss about Bluesky and Nostr?
Both Rachel and Peter suggest that some moderation functionality could/should become part of the protocol stack. #AtProto does composable moderation and that is really cool. Peter hopes that #ActivityPub may learn from it and evolve in this direction.
It occurs to me that while #LinkedData is a fairly bad choice as the extensibility mechanism for #ActivityPub protocol, it should be in theory a rather good choice for the knowledge network and navigation thereof, of the content aggregating into the various federated SO instances.
TBL once asked about using #SolidProject to create a #FAQ and I suggested adding federation to the mix:
Look at how @mikedev designed events in @streams! I would love to see this implemented in other software. @julian have you thought about how @nodebb would display an #ActivityPub event yet? Does @silverpill's @mitra have any support? What about @grunfink's SNAC?
#Ghost#ActivityPub#Decentralization#OpenWeb: "They say the best way to predict the future is to create it, so two weeks ago we shared our intention to connect Ghost with the ActivityPub Network to bring back the open web. We were delighted when our ideas managed to spread even further and wider than we'd imagined, and that so many of you signed up to be a part of the journey."
This feels like a natural next step for @mastowatch but the entire design of the app is structured around Mastodon instance data. I think if someone were going to do something similar for #activitypub at large, it would have to be a different app that is more generalized.
That said, I would love to see someone take the idea and do something for every kind of ActivityPub server/software. I would use it so much. I would probably even add a link to it within @mastowatch.
Bluesky enthusiasts are stating that Bluesky has ”plans” to make ATProto universal and transfer it to W3C or the like. Well, there is no evidence that Bluesky wants to give up control or the protocol is going to be widely adopted after 5 years of development so forgive me being sceptical. The story is a bit different with ActivityPub.
If you're a #fedidev working on an #ActivityPub/Mastodon-compatible server, don't forget that the WebFinger JRD media type is "application/jrd+json" and not "application/json". The early @feditest test results show this is a common mistake.
It's hard to imagine #StackOverflow made their decision without considering the fate #Twitter and #Reddit suffered. That they willingly chose to burn the remaining goodwill they had with their users is bewildering.
Any social web platform could implement E2EE for themselves, but a standardized format will enable users of different Fediverse services to DM each other through the lens of the social platform of their choice.
The whole idea of BlueSky supporting nomadic identities but the rest of the ActivityPub (plus other stuff) Fediverse being unable to do so is such an oversold idea.
A new service using ActivityPub behind the scenes (and not the AT Protocol) can absolutely support nomadic identities, even if the service doesn't treat a whole website as the actor.
It will still use did:plc, same as AT Protocol (BlueSky), but once done so, an application that understands how to work with did:plc can dereference an actor based on the DID.
That said, an existing service will simply not be compatible with this idea, without changing how it operates.
I like @Mastodon, however I am also flirting with the #XMPP could-have-been, @movim as a platform to discover. If only #Movim had proper #ActivityPub compatibility.
I have the feeling that Activity Pub and other new 'protocols' have a different meaning of the term 'protocol'. I mean these APIs and services would not be handled by the IETF. Or do I miss something? #Fediverse#ActivityPub