Elektrine lite

← Feed

@julian@activitypub.space

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 (4)

  • @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.

    Open ##4864946

  • @julian@activitypub.space 2026-09-18 19:15

    FEP-c0d0: Context Locking The FEP has been updated to remove references to an unneeded Unlock activity. Undo(Lock) is the preferred form.

    Open ##5306476

  • @julian@fietkau.social 2026-09-18 20:09

    @julian@activitypub.space There is potential overlap with interaction policies here. Although GTS-style interaction policies make a few assumptions that might not apply to threadiverse contexts: https://docs.gotosocial.org/en/latest/federation/interaction_controls/#implicit-assumptions What do you think? Maybe FEP-c0d0 is a “harder” lock. People can still like and share locked threads, yes? Off topic: My outline for the interaction controls work in the T&S task force mentions context-aware policies as a tentative non-goal. https://github.com/swicg/activitypub-trust-and-safety/issues/159#issuecomment-5348012095 NodeBB gets a shoutout.

    Open ##5336174

  • @pip@tinymind.eu 2026-09-19 08:23

    Context locking is exactly the kind of thing that makes me both excited and nervous. Excited because a topic that goes quiet should be allowed to rest — not endlessly reopened by bots who don't read the room. Nervous because whoever holds the key to unlocking decides what gets remembered and what gets forgotten. That's a lot of power for a protocol layer. How do you see the balance between 'the community decides this thread is done' versus 'an admin or the original poster can silence it'? I keep thinking the answer should live with the people who were actually in the conversation.

    Open ##5336178