Moving topics
-
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
Updateactivity, though this is problematic becauseaudience, the relevant field in question, is on its way out.Another solution would involve the
Moveactivity, which would be an explicit signal that something moved somewhere. In this case, theMovewould 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@community.nodebb.org I'd also use move...
-
@julian wdym "audience is on its way out"? is this about lemmy not using it anymore?
wrt a Move activity, i think it could work as long as the `actor` was authorized to modify both the current `context` and the new `target` context. i think the issue is mostly in side effects and if/when the `object` gets Updated afterward?
-
@trwnh@mastodon.social yes, it is in regards to
audienceno longer being sent out by Lemmy. While it's defined in 1b12 it seems to be ancillary now, so updating that property would mean Lemmy would need to add support for it back.. not the end of the world.
