You might be having a bad day, but at least you didnt spend like a decade developing a social media protocol that was structurally incapable of DMs so you needed to make a whole second E2EE protocol
@fediversereport Thank you for sharing. It is exciting to see what is happening! I think your point at the end is really worth considering: is #Bluesky and the #ATProto interested in multiple apps or is it merely a vehicle for microblogging? I don't have technical background, but I suspect that the decentralization for BSKY is more for show than practice. Critique #ActivityPub all we like but I do think the commitment to platform diversity is there and is practiced.
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.
Ah, I love arguing about #ATProto with people who prefer ActivityPub/fediverse and know very little about ATProto, but have strong opinions about it… 🙃
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.
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.
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 don't know what's the status of the "10 users" limit, at least the Bridgy PDS got it lifted, but even if it's not announced yet I think it's also going away / or will be relaxed soon)
Man, having access to the #Bluesky#ATProto API is like being at a really cool hackathon 24/7, just without the loud music and the noise from the open space… I'm getting ideas faster than I can implement them, I missed this kind of excitement for years 🧑🏻💻💙
“Blacksky is providing a platform to amplify, protect, and moderate Black content so users can safely build community online.
“The mission and purpose of the project is to de-center whiteness as the default and to provide a space for Black folk to discuss the Black everyday in a way that feels affirming.”
Btw, Rust vs. no Rust - rescanning 3 days of posts on the server for the #ATProto feed:
(This is the same #Ruby rake task, but using the native #rustlang module that I've been experimenting with last week to do regexp matching only. Rust version below, obv. 😛)