Same thing for me… I should be hanging out here, where most of the #iOSDev moved. Instead, I'm spending most time on #Bluesky, the #ATProto devs Discord and hacking on various tools for the API, and I try to drag people there one by one.
Not sure exactly what it is that's pulling me there… Some combination of UI/UX, tech architecture, some unspecified "vibe", and the feeling of being a part of something new that's only starting to be built, a "greenfield project".
So I know I am probably going to get biased responses, but please try and be a bit objective. What makes you prefer posting on the #Fediverse over #ATProto / #Bluesky ? I really wanna pick people’s brains on this. I will go first:
I like the concept of portable identity that Bsky talks about however it still feels very much the same exact thing as running your own instance on #ActivityPub but worse as you mainly going to be on PDS that connects to the central BGS that Bluesky operates so you can interact with others, but now they have the power to just block you from everyone else on the BGS… with #ActivityPub you are not having to speak to a centralized BGS you are sending to anything that requests to receive your feed similar to RSS… and you can block still if you don’t want to see stuff from another instance as your instance or personal level without effecting other instances or people depending on the level you block it at.
I've been tracking how the number of posts per day on #Bluesky is going - looks like it's now at about ~400k posts per day from 70-75k users, which is around 4-5x what it was when I started recording data 2 months ago 📈 #ATProto#ATProtocol
(*) I think it's mostly furries though because my people aren't posting much 🙃
This video from @jgarr about the differences between #ActivityPub and #ATProto has me wondering if ActivityPub could actually support separating identity from content, since things like post ids are fully qualified URLs.
Could I host my identity on one domain and my content on another? I haven’t found anything in the protocol spec that forbids that, but I may have overlooked it.