julian@community.nodebb.org 
informapirata@community.nodebb.orgCredo che quando chiedi di spostare un argomento in una categoria remota, intendi anche condividere la discussione in quella categoria remota, giusto?
Yes, but this is what was already happening before.
Of course, the "move" should only be visible on my forum. The move must not (and could not) affect the followers of the original category. It wouldn't even be right for someone to actually remove a topic from one Lemmy community and move it to a different Lemmy community!
And in fact, when I could do this with previous versions of NodeBB, the "move" never affected the federation.
Since I don't write in English and there could be problems with translation, I'll try to explain better with an example:
Starting situation:
- I administer the citiverse.it forum.
- I have decided to "capture" the Lemmy community at https://feddit.it/c/fediverso/
- That community will be visible in my forum at the link https://citiverse.it/category/fediverso@feddit.it
- From that link, my forum users will be able to publish new posts that will also be read by all followers of https://feddit.it/c/fediverso/
- I also decide not to display the communities https://lemmy.lemmy/c/fediverso/ and https://piefed.piefed/c/fediverso/ on my home page.
- However, since I want some topics from the communities https://lemmy.lemmy/c/fediverso/ and https://piefed.piefed/c/fediverso/ to be seen by my users, I have decided to "move" the most interesting conversations so that they can be seen within the community. https://citiverse.it/category/fediverso@feddit.it (as it was before)
- I know perfectly well that this won't actually move conversations from feddit.it to lemmy.lemmy, but this way I get several advantages.
- First advantage: I can avoid creating a local category https://citiverse.it/category/15/discussioni-sul-fediverso-italiano because I will already have a "remote category" https://citiverse.it/category/fediverso@feddit.it (today, however, if I want to move conversations I am forced to do so in a local category).
- Second advantage: if I had two categories on the fediverse, a local category and a community "captured" as a remote category, my users wouldn't know whether to post on https://citiverse.it/category/15/discussioni-sul-fediverso-italiano or on https://citiverse.it/category/fediverso@feddit.it, and this would divide User contributions on topics will inevitably end up in two different categories.
- Third advantage: Furthermore, if my users posted on https://citiverse.it/category/15/discussioni-sul-fediverso-italiano, almost no one would see them, because the Lemmy community https://citiverse.it/category/fediverso@feddit.it has a thousand followers, and I prefer to concentrate the conversations of citiverse.it users in a single community.
- Fourth advantage: When I capture a conversation from piefed.piefed and "move" it to my "remote category" https://citiverse.it/category/fediverso@feddit.it, my forum users will reply to the discussion that started in the original remote category.
- Fifth advantage: If my citiverse.it NodeBB fails to capture posts that a user has decided to publish on the Lemmy community https://feddit.it/c/fediverso/, I can manually move the conversation, and my users won't even notice the technical problem.
13: Sixth advantage: my forum will appear more populated with conversations, making it seem less deserted.
As you can see, I don't want the move to affect the federation, but rather an "optical effect": I want my users to have a better user experience. And I want it to be the same even for those users who don't know or aren't interested in learning about the federation.
To recap
The move should be just an optical effect that only my forum users can see.
I hope I explained myself better.
@julian Now that our server's federation issues have been resolved, I've finally had the chance to fully appreciate the new crossposting feature. It's an excellent feature that provides a great user experience for my forum users.
I should add that this feature also solves at least one of the problems that arose from the inability to move threads to remote categories. If I accidentally moved threads from a remote category to a local one, I couldn't restore the status quo. Today, however, this problem doesn't arise, because the thread remains (also) in its original category.
So, first of all, I'm wondering if you'd reevaluate my observations and arguments in favor of restoring the feature that allowed a thread to be assigned (at least at the local forum level) to a remote community. And, since the new crossposting feature is better suited to this purpose, if you think it's possible to direct crossposting (rather than moving) to remote categories as well.