Comment on Following a Lemmy community doesn't bring in new posts (v4.14.2)
@sj_zero@lotide.fbxl.net @kichae@wanderingadventure.party
No, be careful. We have a terminology problem.
@ska said that there are some remote categories on our NodeBB citiverse.it. Among these, for example, is the category https://citiverse.it/category/test@feddit.it, which represents the Lemmy @test@feddit.it community, which can be found at https://feddit.it/c/test.
So the category https://citiverse.it/category/test@feddit.it is none other than the community https://feddit.it/c/test. (In exactly the same way, the category https://activitypub.space/category/fediverse@lemmy.world is none other than the community https://lemmy.world/c/fediverse.)
The problem @ska pointed out is that for a few months now, if a Lemmy or Piefed user publishes a post on https://feddit.it/c/test, the category https://citiverse.it/category/test@feddit.it takes this into account and represents the post. On the other hand, if the post is published by a social media user (mastodon, friendica, etc.) the category doesn't republish it.
As I already told @julian this is a pretty serious problem, especially since in the past I could at least "move" the conversation manually to the "remote category"; but unfortunately (due to an architectural choice I completely disagree with... oh well! :cry: ), for about ten versions now, it's no longer possible to "move" conversations to just the local categories.
But it should be clear that the main problem is that my system can no longer categorize social posts published in Lemmy categories!
PS: It seems to be a problem with our instance. In fact, I ran some tests:
1: from mastodon to Piefed
https://activitypub.space/topic/6a216416-fa81-49b2-8026-a14feda26556/decentralized-social-media-what-creators-need-to-know-about-web3-platforms
2: from Friendica to lemmy.ml
https://activitypub.space/topic/ebca3327-5273-405c-a5e9-0bd31099d684/decentralized-social-media-what-creators-need-to-know-about-web3-platforms
3: From Mastodon to Lemmy.World
https://activitypub.space/topic/5a2cce1e-64d1-4061-bab6-7043a157ace8/decentralized-social-media-what-creators-need-to-know-about-web3-platforms
And the activitypub.space nodebb catches them all.
On the other hand, citiverse.it doesn't catch a single one! :disappointed_relieved: :face_palm:
@informapirata indeed, I fixed a number of federation issues between NodeBB and Lemmy, in v4.14.0, and again since. I'd recommend updating to the latest stable version and running those federation tests again.
ska@community.nodebb.org 2 hours ago
@julian thanks so much for all the work you've put into ActivityPub for NodeBB, it's genuinely appreciated!
Since you mentioned running federation tests again on the latest stable: we're on 4.14.2 and we're still seeing a concrete issue.
Symptom: informatica@feddit.it (and, similarly, other remote categories) doesn't receive native community posts automatically and new posts always end up in World instead of the category, even though the category is being watched locally.
You can see it directly here: https://citiverse.it/category/informatica@feddit.it : posts there are stuck since June 21st, but https://feddit.it/c/informatica gets several new posts every day, and if we search for them on citiverse.it they do show up, just filed under World instead of Informatica.
Is this one of the gaps you're already tracking? And is there anything worth checking on our end (settings, logs) before assuming it's core-side and happy to pull whatever diagnostic info would help.
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