Comment on Following a Lemmy community doesn't bring in new posts (v4.14.2)
julian@community.nodebb.org 1 week ago In general, moving topics between remote categories is disallowed because it's misrepresentation. You're limited to moving uncategorized topics to a local cid, topics between local cids (of course), and cross-posting topics to local categories.
There are some gaps in federation, as @informapirata states. I've been actively working toward finding and closing those gaps.
@informapirata @sj_zero@lotide.fbxl.net @kichae@wanderingadventure.party
I respect all your work @julian and admire the fact that you've never made a mistake so far. However, regarding moving discussions from one category to a remote category, you're making a error in your judgment.
I may be the one who's missing the point, but if you're available, I can explain in detail all the reasons why allowing the move to a remote category doesn't inconvenience anyone but has only advantages, while preventing this categorization has only disadvantages.
Let me know if you'd like me to continue my argument. Otherwise, if you think it's pointless, I won't continue.
@informapirata ah! I realize that there may be a difference in understanding here.
I think when you are asking about moving topics to a remote category, you're intending to also share that discussion to the remote category, yes?
So, for example, you see a good discussion that comes in uncategorized, and you share it with a community on Lemmy.
Yes?
It makes sense, but I am not able to do that from a protocol point of view because there's inadequate federation vocabulary to achieve this.
So I could make movable, but it won't show up on Lemmy or Piefed unless that software supports whatever vocab I come up with.
So it's partly a technical limitation as well.
@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.
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:
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.