2026-09-18 17:49 UTC
FEP-c0d0: Context Locking
This is the main discussion thread for the draft FEP-c0d0: Context Locking
Summary
Context locking (and its inverse, unlocking) refer to the action whereby a topic no longer accepts new replies.
This proposal introduces a locked property on the context object, and a new activity type, Lock, to signal changes to a topic's locked state across the fediverse. Unlocking is expressed with the standard ActivityStreams Undo activity, applied to the original Lock. It builds on FEP 1b12: Group federation for audience identification (the audience property) and the Announce wrapping pattern, and on FEP fe34: Origin-based security model for authorization.
This FEP is a sibling of FEP f15d: Context Relocation and Removal, which covers the Move and Remove moderation actions.
The full FEP text can be found at https://w3id.org/fep/c0d0
Replies (1)
-
@flamingos@feddit.uk 2026-09-27 03:21
In Lemmy, object is the post itself — a Page (Note-like) object. Lemmy has no separate context abstraction: the top-level post is both the root object and, implicitly, the thread, so pointing object at the post is sufficient to identify the thread being locked. I’d just like to point out that in Lemmy 1.0 a Lock can also point to a Note (comment under a post in Lemmy lingo) so that only that comment and all its children are locked, while the rest of the thread remains unlocked. I believe Piefed already works like this as well.