Thread (right-hand) frame slow/stalling

From: CHYRON (DSMITHHFX)17 Apr 10:44
To: ALL1 of 9
When I click a thread link from the list (left-hand frame) the thread frame doesn't load for long periods if at all.

This has been happening on and off for a few days. Sometimes it clears right up (as now), sometimes it persists past restarting Firefox, leading me to believe it's a server or network issue. Our not-so-broadband can be choppy, but the issue doesn't appear to affect loading from other sites quite so dramatically.

Firefox on Fedora 40 (Gnome 3x) desktop. Not happening on mobile (Samsung A7 tab).
EDITED: 17 Apr 10:45 by DSMITHHFX
From: Drew (X3N0PH0N)17 Apr 16:10
To: CHYRON (DSMITHHFX) 2 of 9
Yup, getting the same. Clicking the thread a few more times usually fixes it.

I assume the server is basically just in maintenance mode these days.
From: CHYRON (DSMITHHFX)17 Apr 16:52
To: Drew (X3N0PH0N) 3 of 9
Well it's weird that it works as per usual on mobile.
From: william (WILLIAMA)17 Apr 17:34
To: CHYRON (DSMITHHFX) 4 of 9
...and it also seems OK on Windows 11.
From: CHYRON (DSMITHHFX)17 Apr 22:31
To: william (WILLIAMA) 5 of 9
Same here on 10. I should probly run an update on Fedora, been a few months.
EDITED: 17 Apr 22:32 by DSMITHHFX
From: Drew (X3N0PH0N)18 Apr 10:47
To: CHYRON (DSMITHHFX) 6 of 9
I assume it's a firefox-on-linux thing then. Which is unsurprising. Mozilla never gave a fuck about linux, even when they were markedly less shit than they are now.
From: CHYRON (DSMITHHFX)18 Apr 10:58
To: Drew (X3N0PH0N) 7 of 9
I haven't updated it in months, and this just started a few days ago, so maybe not.

Anyway, working fine this morning.
EDITED: 18 Apr 11:07 by DSMITHHFX
From: Peter (BOUGHTONP)18 Apr 13:38
To: ALL8 of 9
I haven't experienced this. (Firefox ESR on Debian)

Linode sent a high CPU warning about a month ago now (not something I've received before), but I don't recall noticing any issues - I assumed it either resolved itself and/or Matt restarted the server; since there haven't been any more warnings I assumed it was a one-off and nothing to worry about.

One possibility is aggressively crawling bots - in the past I've had issues with Semrush bot and a few others and blocked them - so maybe we need an updated robots.txt - it's a low-effort first step at least.

EDITED: 18 Apr 13:41 by BOUGHTONP
From: CHYRON (DSMITHHFX)18 Apr 16:06
To: Peter (BOUGHTONP) 9 of 9
I've heard of AI bots scraping websites for "training" (plagiarized) content causing load issues.