Interesting federation jank between Mastodon and multiple nodeBB sites
-
I was looking at this post from my own forum (nBB 4.0.3) via various vectors, and trying to pull it in from here resulted in a couple of hiccups.
- Searching the posts community.nodebb.org URL did not pull the post and its comments. Naturally, searching the original URL works fine (though does not fetch the comments, naturally)
- Fetching my comment from that post does fetch the post and full comment chain, but your comment, @julian, is surprisingly empty (link)
Just thought you'd like to know.
-
I wonder if it is related to the recent change that showed an "in reply to" bar above a post? I've noticed that that is sometimes empty too.
> Searching the posts community.nodebb.org URL did not pull the post and its comments.
It should've, what URL did you specifically try to pull?
This URL should pull the entire topic:
https://community.nodebb.org/topic/d9a56cb0-3d17-4d72-a9f7-592421e1c9d1/what-s-a-good-lightweight-good-moderation-tools-foss-forum-system-these-days
This URL (the original post's original URL) should pull only the OP:
https://mastodon.neilzone.co.uk/users/neil/statuses/113991455813168788
As for my comment being empty, does it come back if you restart your NodeBB? Not that you should need to, just want to see...
-
@julian That's the URL I've tried to use. It just won't fetch it for some reason. But if I search any of the comments, it'll pull it in just fine. https://community.nodebb.org/post/103252, for instance, pulls the whole thread in.
Restarting nodeBB renders your missing comment, though!
-
@Kichae thanks, will have to play around a bit to see what's going on.
-
@Kichae the github issue is here:
Reports of blank posts · Issue #13172 · NodeBB/NodeBB
There are reports of blank posts appearing on NodeBB. They are related to remote posts who have markdown defined. At some point in the logic the post is parsed with the empty content and cached as empty. A NodeBB restart usually temporar...
GitHub (github.com)
I think I found the source of the problem and fixed it. Try updating to the latest
master
ordevelop
commit and see if it still happens. -
I can no longer reproduce the issue!