Recent searches
Search options
Administered by:
Within the context of threaded discussions, contexts (aka "topics", "posts", "threads", etc.) are associated with an audience (aka "forum", "category", "community", etc.).
What happens currently when a context is moved from one audience to another? How does ActivityPub enabled software communicate this?
I recently moved this topic from one category to another, and in doing so, realized that I have absolutely no idea what happens to the group association as seen by other software.
@rimu@piefed.social also said in the other thread:
Also moving what NodeBB calls a topic (a post in Lemmy/PieFed) from what NodeBB calls a category (community in Lemmy/PieFed) into a different category (without spawning a new topic or leaving the old copy behind) is much needed but not implemented in Lemmy/PieFed/Mbin.
One solution would be to federate an Update activity, though this is problematic because audience, the relevant field in question, is on its way out.
Another solution would involve the Move activity, which would be an explicit signal that something moved somewhere. In this case, the Move would indicate the context moved to the new audience, or in AP software that have not implemented FEP 7888, then the top-level object will have moved to the new audience.
cc @andrew_s@piefed.social @melroy@kbin.melroy.org @bentigorlich@gehirneimer.de @nutomic@lemmy.ml
@julian @rimu@piefed.social @andrew_s @melroy @BentiGorlich @nutomic Conceptually I quite like `Move` because `Update` would tend to be done by the original author of the content. Whereas `Move` would often be done by a moderator. Also there may be (?) a new workflow involving an `Accept` from the moderators of the destination audience.
Also there may be (?) a new workflow involving an
Acceptfrom the moderators of the destination audience.
Thanks for calling that out, that's a legitimate use case that I would not have anticipated.