Kichae does the category show as having followers? (If the remote category doesn't have followers there will be a little warning note before the topic list.)

I do have a few categories I follow here and they seem to be working, though they may not be Lemmy specifically.

Was [email protected] one of them?

julian No, [email protected] isn't currently being followed, and it shows the warning, but all of the ones in the screen shot above are from this forum, are being followed by me, and haven't received a new topic in 8 days. [email protected], in particular, is almost hyper active right now.

Kichae thanks, I'll take a look ASAP

New observation: I'm still receiving notifications for up/down votes from Lemmy, but no other content.

Hmm... I am not sure whether it is significant, but I am still getting topics from one of my communities. That's why I was not aware that federation was broken.

It does suggest that it's a NodeBB-specific bug though...

I tested on a dev instance with a lemmy test group and found nothing wrong. Two-way posts work, as do upvotes.

I can definitely confirm that followed communities here aren't working, which is concerning. Not sure why yet.

After more debugging today I am less convinced that this is a NodeBB issue.

I am finding Lemmy communities where federation continues without issue, and others where there is no activity at all.

The sequence of events is:

1. NodeBB sends out a Follow
2. Lemmy responds with a 200 or equivalent
3. Lemmy later sends me an Accept
4. Lemmy later sends content (posts, upvotes, etc.)

startrek.website and ani.social both do everything ok.

lemmy.world and mander.xyz fail at step 3, and existing connections (where step 3 completed in the past) do not execute step 4. I literally am not seeing anything besides Like activities coming from those servers.

Existing PieFed and NodeBB integrations continue to work without issue.

@[email protected] I'm actually having trouble getting new ani.social posts into my instance. I'm not sure if @[email protected] is having the same problem, but it seems that it grabbed posts from up to 9 days ago, and then stopped federating them in.

It says Asserting 0 group(s) when I check the remote category on my instance directly though, so perhaps this is related?

@julian On my implementation, I have not received anything actionable from a lemmy instance recently, but I purge remote posts after about a week. So this may not be NodeBB related. I am following some lemmy.world and lemmy.zip communities. The last federated lemmy activity I received originated at lemmy.ca 4 days, 19 hours ago.

Wild.
What's really weird is that I know I stopped receiving topics and posts from all of the Lemmy servers I follow communities on on the day I graded from 4.3 to 4.4.1, which was several days after this forum was updated to 4.4.1. Meanwhile, those communities here stopped receiving topics and posts a few days earlier than my forum did (though, I can't say for certain that that was on the day y'all updated to 4.4.1).

My follow relationships are rather mature at this point, so it's not like this is an issue with establishing new follow relationships. Old ones are broken, too. Very strange. And also, FWIW, very unidirectional: I can still post into these groups and have my content federated. I'm just not processing or receiving anything coming back my way.

I'm up to my eyeballs right now, but I'll try to look more closely into logs this weekend to see if I can identify any paradigm shifts.

Kichae I suppose it's worth rolling back to 4.3 and figuring out what the change was...! I just wish testing federation wasn't such a long process.

It is rather silly that it inter-platform federation so damn fragile. I can't wait until there's a bigger network of nodeBB sites federating.

Confirming that follow-unfollow-follow-unfollow logic is working as expected against ani.social which means the plumbing actually works.

[email protected] did you update NodeBB 9 days ago?

@[email protected] not to my knowledge! I actually reset my instance within the past 7 days, so it's unlikely to be that if I'd guess. It could be an upgrade related script didn't fire, but that's pure speculation