@kichae@community.nodebb.org can you try again with the latest develop commits?

A couple things:

• You can now set the rate limit value to 0 to disable it completely
• The logic was a mix of both a db-backed mutex lock and a rate limiter, which was overkill. I think what happened was Lemmy (or other popular instances) sent many activities all at once, causing the rate-limiter to trip, even though the value was well under the threshold.

The default is now updated to 256 but if you've overridden it your value stays. I'll keep an eye on Lemmy federation to see if that was the issue...

If I am right, then within the next 6-24 hours, I should be receiving a flurry of Lemmy content as it speedruns through the backlog.

https://github.com/NodeBB/NodeBB/issues/14422 for updates.

As it turns out I was not right, at least not entirely <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f61b.png?v=db237af6dbe" title="" />

Yeah, I'm not seeing anything behaving differently on develop. My logs are super clean now, though.

@kichae@community.nodebb.org hopefully this will be something that we'll see results on within a day.

Once Lemmy decides your server is "down", it won't send anything for awhile. How long that is I don't know offhand.

@kichae@community.nodebb.org

Heckin' yeah. Update to the latest develop again.

For me, lemmy.world hasn't started re-sending activities yet, but it will... <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f440.png?v=c7cc56fe415" title="" /> There it goes... 5 million activities an hour hahah

Better, but it's not over yet:

Error rates have crept back up, so there's more debugging to do.

I wonder if there was some change on Lemmy's end. I stopped following its development some time ago after nbb started filling all of my Fedi needs. I did notice that one of my latest posts was rendered by Lemmy as raw texts showing all of the Markdown syntax and ignoring line breaks, which I don't remmmeber being an issue before. Though I guess that might also be plugin related.

@Kichae hmm if there was a rendering issue on their end it could be either end (sender or receiver). Can you share the post?

You can see the effect here, with the quote block not being rendered: https://lemmy.ca/post/67342849 It seems like it might actually only be select Markdown that's causing issues, or maybe even only the quote block notation.