Samuel
underrated part of atproto is most of the time you don’t have to directly talk to other people’s (possibly badly made) servers, it’s all mediated via records
Emelia@thisismissem.social· 4 Jul
Oh dear lord, I knew it was bad, but didn't know it was this bad: hackers.pub/@fedify/2026... (I've mostly just contributed to activitypub projects that already existed, so didn't usually need to experience these specific pains)
Why implementing ActivityPub is hard, and why it doesn't have to be
Implementing the ActivityPub protocol from scratch introduces massive technical hurdles, including fragmented signature standards, unpredictable JSON-LD document variations, complex distributed system...
hackers.pub
6 19 133
Emelia
You can still umm, have badly written records or missing lexicons.. and sometimes you deal with someone's non-spec implementation of oauth
1 11
Samuel
@samuel.fm
oh for sure, you still have to work with other parties at the end of the day, they’ll inevitably find ways to let you down. at least the surface area is much reduced
1 10
Thoth
Also we don't use RDF and don't have to worry about RDF canonicalization. (I'm not going to do my RDF rant again. Just... kind of take it as read that it goes here.)
1 2
Emelia
There's dealing with different lexicons or technically invalid record data, and then there's RDF for sure. As i've noted when talking about Solid: RDF was one of the biggest stumbling points in people trying to adopt it.
2