Significant site performance updates - Early Nov 2025

Posts
34,777
Likes
39,344
Hi, you might have noticed the site running quite a bit faster, we actually haven't increased our server hardware, in fact we're hoping to slightly reduce and consolidate it, but we're using it a great deal more efficiently than before so hopefully page loads should be much faster.

If you notice any issues, please let me know in this thread so I can check them out.
 
Posts
18,149
Likes
37,886
The problem i had with pages stalling on load in Safari has gone.
Pages and refreshes are nice and snappy now.

🫡
 
Posts
34,777
Likes
39,344
The problem i had with pages stalling on load in Safari has gone.
Pages and refreshes are nice and snappy now.

🫡
Oddly it wasn't specifically meant to address that, but it does seem to have resolve it for me too in Safari, I haven't seen it in several days now.
 
Posts
29,870
Likes
77,285
The last day or two, when I just hit refresh in my browser (Edge) some threads that were unread, switch to being read.

The very pale blue highlight disappears, and when I click on the thread it does not take me to the last post, but to the start of the thread.

 
Posts
34,777
Likes
39,344
The last day or two, when I just hit refresh in my browser (Edge) some threads that were unread, switch to being read.

The very pale blue highlight disappears, and when I click on the thread it does not take me to the last post, but to the start of the thread.
I’ll have to get @Trev to check that out, which windows version is this running on?
 
Posts
29,870
Likes
77,285
I’ll have to get @Trev to check that out, which windows version is this running on?
10
 
Posts
2,385
Likes
3,120
The last day or two, when I just hit refresh in my browser (Edge) some threads that were unread, switch to being read.

The very pale blue highlight disappears, and when I click on the thread it does not take me to the last post, but to the start of the thread.


Just a heads up, clicking any of these always take you to the last post.
 
Posts
29,870
Likes
77,285

Just a heads up, clicking any of these always take you to the last post.
I know…I usually don’t have to…
 
Posts
427
Likes
821
The last day or two, when I just hit refresh in my browser (Edge) some threads that were unread, switch to being read.

The very pale blue highlight disappears, and when I click on the thread it does not take me to the last post, but to the start of the thread.

I'm having the same trouble on Chrome. The 'Latest' page opens with all the unread topics marked appropriately, but as soon as I read one topic and refresh, half a dozen unread topics are also marked as read. This happens every time I read a topic until almost the whole page is marked as read. It's been happening for the past couple of weeks.
 
Posts
5,527
Likes
9,447
Same issue with me, on both home and work computers. So Win10 and Win11 machines, both with current Chrome versions.

I use the "New Posts" to bring up the threads that have been updated since I last viewed, and many I have not read, or only partially read, show up as having been fully read. Clicking on the thread takes me to the last post instead of the first unread post.

This has been happening for a week or so.
 
Posts
34,777
Likes
39,344
Same issue with me, on both home and work computers. So Win10 and Win11 machines, both with current Chrome versions.

I use the "New Posts" to bring up the threads that have been updated since I last viewed, and many I have not read, or only partially read, show up as having been fully read. Clicking on the thread takes me to the last post instead of the first unread post.

This has been happening for a week or so.
We're looking into it now, appreciate the feedback
 
Posts
2,385
Likes
3,120
@Archer and @TasMike we think that hovering over threads with your mouse cursor on desktop was likely marking threads as "read" in some cases, so we've made some config changes to address the issue. Behavior should be back to normal now. 👍
 
Posts
427
Likes
821
@Archer and @TasMike we think that hovering over threads with your mouse cursor on desktop was likely marking threads as "read" in some cases, so we've made some config changes to address the issue. Behavior should be back to normal now. 👍
Fixed! Thanks Trev