The AT Protocol is becoming an IETF standard. What that means and why it matters.
Power asymmetries have consistently driven the pursuits of egalitarian ideals. Some of them had lasting consequences: Athenian democratic reforms, the Gracchi brother's land reforms in Ancient Rome, the Venetian republic, the Peasants revolt in the Middle Ages, and the French Revolution are just a few examples.[1]
The first cohesion spectrum was simple and formed a nice acronym, CABIN. It had some zones right. It also had serious issues, but exposing them was helpful in this journey. When trying to find solutions for them, I realized two things. One is that I need to account for both the autonomy cost and autonomy gain of being within a particular coordination regime. After some iterations, it got substantially better, but I'm still not happy with it, so the second thing I realized is that I need help, hence this draft, which is an RFC, Request For Comments. Unlike IETF RFCs, the intention is not to be the de facto released version, but rather a way to get to a better one.
A core maintainer's reflection on a year of Model Context Protocol, coinciding with the 2025-11-25 specification release and a look at what's next.
For today, the first day of my 30 Days of Protocols, I'm just following the ATProto Quickstart Guide. It's a fun opportunity to work with JS after largely living in Python land for the last few months. This is probably pretty easy and straightforward if you're not a Windows idiot like me (the general consensus from ATProto devs seems to be that Macs are superior, which I don't disagree with. However, I am stuck in Windows land for the foreseeable future, so I have to live like this regardless).
Nostr is another effort to build an open social network on the Web, and it's very different than ActivityPub. Here's how it works.
Why unencrypted IMAP transmits credentials and message contents in plaintext over the wire, and the case for switching mail clients to SSL/TLS.