J
@malte@forum.fedi.dk @Kichae I tested the following use cases:
All cases worked okay. Potentially this was fixed already with some other unrelated fixes?
@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…
@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?
@malte@forum.fedi.dk are you able to run the forum in dev mode?
Only then will ActivityPub logging be enabled. Once that is being logged, try the follow again and let me know what errors show up.
@trwnh@mastodon.social correct. I suppose the easiest way to communicate permission would be that the thread deletion has to come from the context owner. In my case the context owner is a category, so it’d be federating out the deletion on behalf of the moderators.
@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.
Hi @malte@radikal.social! We actually have an issue open for that:
https://github.com/nodebb/nodebb/issues/13127
Basically we should make it more readily apparent that a category can be followed and posted to.
For Mastodon you have to mention the category. Mastodon conflates addressing and notifications.
Other software could potentially address the category instead of mentioning.
@wjmaggos@liberal.city that’s true for Mastodon, but not for other servers with more of a community focused aspect, like NodeBB.