Week in Fediverse 2026-09-11

Release v3.12.1 patches a bug that's been present for about two years and fixes issue #163 in the process. Looking at FediDB, it appears most servers on v3.X.X made it through the upgrade to v3.5.0, which is where the bug would have bitten, but the consequences of the bug are annoying enough that a patch is warranted.

Changed

• Gather query planner statistics on startup and before reconciling materialized views.

Up-to-date query statistics ensure that the expensive migration in v3.5.0 completes in seconds or minutes, instead of hours!

#ktistec #crystallang #activitypub #fediverse

I had success running #meshtastic during #dragoncon in Atlanta. Most of the con there were ~60 nodes directly reachable and 500+ visible in the metro area. Which is pretty cool.

I'm now in the four corners area outside of Orlando, and there is zero activity that I can see. I had to reinstall the regular (non-DragonCon) firmware, and maybe I screwed that up. Or maybe I'm just too far out in the boonies.

I'm still pretty new, so if anyone in the Orlando area has tips, reach out!

my hot take: LLM-based AIs are going to be classified as weapons

made my first connection on #meshtastic at #dragoncon

This release encompasses two broad sets of changes: widening the pool of candidates for feeds and more carefully checking the origin of inbound activities (broadly FEP-fe34, Origin-based security model).

Candidates for feeds were originally limited to posts in the actor's mailboxes. This decision made authorization easy but omitted clearly acceptable posts (for example, posts addressed to the public collection) that arrived via other means (for example, filling in a thread).

Prior to this release, inbox processing did not consistently define an object's origin nor did it apply consistent rules to what it admitted based on the origin.

FEP-fe34 is still not fully enforced, and truth be told, I'm still reviewing some of its mandates, so I'm not yet listing it in Ktistec's federation documentation.

Here's the full list of changes:

Added

• Notify a deck pane when it has new posts.

Fixed

• Retry an unresolved quote authorization.
• Label a draft with the status of its quote request.
• Compare origins when deciding whether to trust an IRI, key document, or owner.
• Ignore a trailing slash when matching a dereferenced document's IRI.
• Allow only Create and Update to update objects.
• Ignore an inbound vote that fails the FEP-9967 checks.
• Expand commonly omitted ActivityStreams context terms.
• Break a long link rather than let it overflow.

Changed

• Widen the feed scan to every object the server holds.
• Address a published feed by slug rather than by id.

Removed

• The proxyUrl property from the actor document.

I am still working hard on the feed deck. Both notifications and feed ordering now work. It's now my preferred reading interface, and should be ready by the next release!

#ktistec #crystallang #activitypub #fediverse