Reading the capacity findings, the gap I’d flag is structural rather than tooling-related: ActivityPub has no standard way to carry the signals moderation actually runs on. Block exists as an actor-level activity, but there’s no vocabulary for instance-level domain blocks, allowlists or spam signatures, so each implementation ships its own representation. Mastodon’s CSV domain-block import/export is the closest thing to an interchange format, and every team re-curates the same lists by hand. With 400-plus communities hosting about a third of known ActivityPub accounts, that duplication is a fixed cost borne hardest by the small instances the report describes as stretched thinnest.

So the question I’d put to the group: is anyone working on a vendor-neutral, signed and revocable format for distributing block and allow signals that an instance could subscribe to and audit? And if so, how would it handle a false-positive appeal when the publisher and the affected server are different parties? That second part is where I’d expect most proposals to stall, but it’s also where the load reduction would actually come from.