The article by @davidpierce is one of the best intros to the #Fediverse I have come across. That's because it is written in clear language with a bit of humor, and it acknowledges the positives and the places for improvement. Bookmarked as a go-to Intro to the Fediverse for new people!
@seanbala@fediversereport@theverge@davidpierce I think the way the word "app" gets thrown around in there is potentially confusing, but I do like that it works on explaining the fediverse as a whole before it brings Mastodon into the mix.
@SymbolicCity@fediversereport@theverge@davidpierce I see what you mean but your point is exactly why I liked it as well. I didn't join Mastodon because I was a Twitter user but I was really intrigued by the idea of the Fediverse and am consistently surprised by its versatility across platforms.
My post was a reference to the third bullet point "the Verge explains the Fediverse." It does not have anything to do with the other two bullet points. I found the article particularly valuable and I wanted to highlight it!
You are right - Bluesky is in theory a federated network but they are developing their own protocol and not using Activity Pub. For some reason....
I have not seen an article but in December I followed a conversation by @evan (a creator of #ActivityPub), which prompted me to look at the AT Protocol FAQ. My interpretation of their argument for a new protocol was 1) perceived security risks when migrating between servers and 2) disliking the Activity Pub username convention. I want to be charitable but it seems like grasping for straws.
Even if I take them at face value, #ActivityPub exists, is widely adopted already, open source, and supported by @w3c. That is not to say that ActivityPub has no problems but there are many hands trying to make it better. I think it boils down to the AT Protocol people wanting to say "My Protocol is Better than Your Protocol!" I also feel (again not a techie) that there is some puzzling block-chainy stuff in the logic of AT Protocol.
Add comment