TECH Signal 397
ActivityPub co-author credits the protocol's deliberately ordinary design for its success
↗
Evan Prodromou's FediForum talk argued that ActivityPub's intentionally unremarkable architecture, HTTP, JSON, and inboxes/outboxes, is why it spread across the Fediverse.
For engineers building federated systems, the talk highlights that a minimal, unexciting protocol can achieve broad adoption. It also shows that such pragmatism accumulates technical debt, as seen in the Fediverse's reliance on an expired HTTP Signatures draft.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
ActivityPub's core is deliberately ordinary, using HTTP, JSON, URLs, and actor inboxes/outboxes.
The protocol's minimal agreement lets diverse platforms federate without unifying their databases or moderation models.
The Fediverse's use of the expired draft-cavage-http-signatures-12 conflicts with the later RFC 9421 standard.
THE CLUSTER