Uncategorized

I don’t spend much time on software engineering industry reports, but the Thoughtworks Radar is one I love. Broad, clear-eyed, hands on, eminently useful. Bite-sized analyses of ~100 tools and techniques, new and old, with recommendations to adopt or trial or assess or hold, and a brief nod toward overarching themes. It’s evidently become so successful that it’s spawned an entire category.

The latest volume came out last month, and as usual, it’s a banger. I’m only maybe a third of the way through, and I already have todos to learn more about run cost prediction, accessibility testing, and Logseq, among others.

Free, ~40 pages, twice a year. Not an ad, I have no affiliation with them, just a fan.

Standard
Uncategorized

One core difference between the fediverse and the AT Protocol seems to be that AT decouples many key building blocks – identity, moderation, ranking algorithms, even your own data to some degree – from your server. The fediverse, on the other hand, ties them all to your server and sees that as a desirable feature.

The fediverse says, choose a server that you identify with as an individual, with admins who moderate according to your values, and a local timeline that you like reading.

The AT Protocol, on the other hand says sure, choose all of those, but independently from your server, and keep those choices if/when you migrate to a new server.

Interestingly, I don’t think much of this is really driven by ActivityPub itself except identity. Third party AP moderation tools could easily be built, and probably have been. Same with clients that rank your feed with custom algorithms. This seems like more of a cultural difference, a difference of values and philosophy about how social networking should work.

Standard