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?
"In 2024, for the first time, it finally feels like we have a critical mass of people and platforms who are interested in rewilding the internet to bring back what we lost, and create something new. ... There's a palpable feeling that this just might be the year of the open web."
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.
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.
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.
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.
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.
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
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'm following this tutorial by @Gargron, does anybody know if this is still up to date? I can't get Mastodon to find my test-actor in search. The inbox exists and can be posted to, the actor verifyer tools tell me it that it should be valid. I can see in my logs, that the mastodon instance I am searching for is accessing my actor endpoint, but in search, it tells me nothing can be found
I actually started #Fedify because I was working on a single-user #ActivityPub implementation called #Hollo and felt like I needed some groundwork, and now that I'm somewhat done yak shaving, I'm back to working on Hollo, although I still jump back and forth between Hollo development and Fedify when I think of features I need for Fedify.
So #Bluesky is implementing an (unspecified) new protocol for direct messages. Because AtProto is really not suitable for anything that isn't 100% public.
I wonder whether they can do this now that Jack is off the board. But maintaining two separate protocols in the same app? Who knows, maybe #ActivityPub is next?
A little bird told me that when #Threads will be totally into #ActivityPub then #Mastodon will mysteriously lose the ability to block entire domains/servers... 🐦
Looking into this Summer of Protocols thing that @evan and @tomcoates got accepted for to work on adding encryption to #ActivityPub, and realized its a grant from the Ethereum Foundation. I am not opposed to crypto slush money flowing into more useful projects like the #fediverse but thought it was interesting that I hadn't seen anyone mention this fact yet.