@julian

FEP-f15d: Context Relocation and Removal

I have two objections to this proposal. We discussed them before in Moving topics/contexts between communities:

1. It assumes that a context always belongs to one group.

As I suggested in the aforementioned thread, an Update activity is a better solution because it works when relationship between a context and a group is many-to-many. It is also semantically cleaner: "update collection audience" instead of "move collection from actor 1 to actor 2" and "remove collection from actor" (at least if ActivityStreams terminology is used).

2. Treating collections (dynamic views) as static objects that can be moved, deleted etc is not compatible with client-side signing.

One possible solution is to separate context (an object) and its contents (a collection).

@jesseplusplusJesse Karmani @rimu @nutomic @melroy @BentiGorlich

@silverpill@mitra.social said in Minutes from 4 December 2025 WG Meeting:

  1. It assumes that a context always belongs to one group.

Yes that's correct. There was the potential for a context to belong to multiple audiences but social issues preclude further research.

Specifically, moderation gets very messy when contexts are cross posted to diametrically opposing audiences, and so that's not something I am equipped to work through right now.

Secondly, the assumption is already there that a context only belongs to one audience. We will not change that expectation.

0

If you have a fediverse account, you can quote this note from your own instance. Search https://activitypub.space/post/735 on your instance and quote it. (Note that quoting is not supported in Mastodon.)