Forums and Threaded Discussions Task Force

0 readers

1 users here now

Discussion and announcements related to the SWICG Forums and Threaded Discussions Task Force.

This profile is a discussion forum category and shares content from users who post in its discussions.

This is a forum category containing topical discussion. You can start new discussions by mentioning this category.

founded 5 months ago

Moving topics (community.nodebb.org)

submitted 3 months ago by julian@community.nodebb.org to c/forum-wg@community.nodebb.org

3 comments fedilink hide all child comments

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

top 3 comments

sorted by: hot top controversial new old

[–] rimu@mastodon.nzoss.nz 2 points 3 months ago (1 children)

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

[–] julian@community.nodebb.org 1 points 3 months ago

> Also there may be (?) a new workflow involving an Accept from the moderators of the destination audience.

Thanks for calling that out, that's a legitimate use case that I would not have anticipated.

[–] BentiGorlich@gehirneimer.de 2 points 3 months ago

@julian@community.nodebb.org I'd also use move...