J
@Kichae @malte@forum.fedi.dk as you two have discovered, topic management tooling for remote topics is far less exhaustively tested 
The move post functionality specifically I don’t think has been tested at all, so:
https://github.com/NodeBB/NodeBB/issues/13204
@Kichae said in Moving a federated post into another topic:
> merging remote topics
Merging two remote topics together? Or one remote and one local?
@wjmaggos@liberal.city that’s true for Mastodon, but not for other servers with more of a community focused aspect, like NodeBB.
@malte@forum.fedi.dk this is the issue you’ll want to subscribe to:
https://github.com/NodeBB/NodeBB/issues/12435
I think NodeBB tags are always lowercased, which is something we could reconsider…
@reynir@forum.fedi.dk the post content being blank issue might be an unrelated bug. I’m still trying to figure out that one.
@reynir@forum.fedi.dk there wasn’t, so I added one:
@trwnh@mastodon.social OP shouldn’t necessarily be able to unilaterally delete their thread, though.
At least it doesn’t work that way in forums, but I can see how it would be different based on implementor expectations.
@niels @Kichae @eeeee what specifically you’re asking for here is a way to retrieve the entire conversation, all branches of it, for the full context.
This is not something ActivityPub can do currently by design. However I am working with a number of separate implementors to establish something like this. You can see the progress of our efforts here:
https://community.nodebb.org/topic/18647/the-state-of-conversational-contexts-february-2025
This is already working in the wild. If you attempt to pull any post from NodeBB, you will get the entire topic, including remote replies.
Mastodon is separately working on something called “reply tree traversal”, which is something that will also work but is an approach I feel is fraught with reliability issues.
@malte@forum.fedi.dk yes, because you are using NodeBB. It will send the activity to as many people as it possibly can, who have any relation to the topic.
Hello all 
Today we’re releasing NodeBB v4.2.0. Most of the changes pertain to minor updates to our existing ActivityPub integration.
The “View Original” button for user profiles is located in the sidebar of any remote user profile:
silverpill@mitra.social dansup@mastodon.social we’ll reach out to the owners of the two top forums and suggest enabling federation.
The FEP is also great, we’ll be following along and implementing.
Keep in mind federation can be turned on but no categories federate, so perhaps that case needs to be called out.
Kichae thanks, I’ll take a look ASAP
Kichae re:
> so giving registered-users privilege back to -1 worked?
can you let me know if the registered-users bug is still occurring? I am wondering if I patched it in the course of regular development.
Here’s the post here: https://community.nodebb.org/post/https%3A%2F%2Fforum.fedi.dk%2Fpost%2F1436
Seems the images don’t load due to cross browser security settings
malte@forum.fedi.dk one other thing.
There are some shifting specifications related to how long-form text is handled. Specifically, NodeBB is on-track to follow FEP b2b8: Long-form Text.
Part of that means that topic OPs are federated out as Articles without inline images convertd into attachments, because they are technically not attachments. This means right now Mastodon will not show the media at all.
Mastodon will implement this FEP eventually, which means it will properly handle the attached Note preview, which does contain the attachments.
NodeBB can better handle the images coming from other NodeBBs, though. That’s a bug.
Rp1 couple things here…
If you want to enable SSO via your own IdP, use nodebb-plugin-sso-oauth2-multiple. That will allow you to configure a client without having to actually code… ideally.
If you want to have an auth cookie shared between subdomains, use nodebb-plugin-session-sharing.
phenomlab ah good to hear, thanks, and sorry about that!
We’re not quite sure what happened with the eslint update that caused existing installs to complain so loudly.