The logic is a little tricky to get right because there’s a set sequence of steps that needs to happen in order for the group sync to succeed.

For example, between NodeBB and Lemmy:

1. NodeBB admin tries to follow a Lemmy community
2. NodeBB marks the follow as pending
3. Lemmy records NodeBB as a follower
4. Lemmy community tried to send an Accept back
5. NodeBB marks the follow as established.

If steps 1-3 succeed but 4-5 fail, then posts might be sent to NodeBB, but NodeBB will silently drop them because they’re not addressed to anyone it thinks is following the sender.

@freamon thanks for the heads up about lemmy’s accept shenanigans, I’ll take that into account… or maybe ask Felix about it.

@arachnibot @FrankM

@arachnibot happy to take a closer look, since the category sync functionality should be working but might have broken in the interim during development.

Can you let me know the Lemmy community you’re trying to follow from your instance?

@scott@loves.tech looks like you found a bug!

https://github.com/NodeBB/NodeBB/issues/13070

The emoji normally show through fine but yours don’t because you send markdown and we parse it on demand. Will have to refactor!

@scott@loves.tech just mention the category actor in a new post and NodeBB will associate it with the category 🙂

@altcode@social.vivaldi.net thanks for reporting. It’s a persistent bug that has been evading capture for some time.

For whatever reason, occasionally some accounts will lose their handle-to-id association in the database. That is why you are not able to access the profile page, because NodeBB doesn’t think it exists anymore.

For now the workaround is for me to manually reassociate, but I still have not figured out the root cause of the issue.

testing @altcode@social.vivaldi.net and @vivaldi@social.vivaldi.net

@sabrew4k3@lazysoci.al ah I think I can explain that… an unrelated boost caused my instance to fall over for a little while heh.