Anonymous B joined in and replied with this 1 year ago, 1 hour later[^][v]#1,324,594
Agree, it leaves you at the top of the thread. Also if you then go back it used to be the new replies number was gone but now it still displays until you manually refresh.
tteh !MemesToDNA joined in and replied with this 1 year ago, 10 minutes later, 3 hours after the original post[^][v]#1,324,612
@OP
When did this start happening? I've not had that issue (yet) but I'll look into it. @1,324,594 (B)
Ugh I did notice that a while ago myself, but I thought it was a caching issue on my end. :(
Anonymous I joined in and replied with this 1 year ago, 7 hours later, 15 hours after the original post[^][v]#1,324,667
@1,324,602 (Dana !N3luHurry2)
You can use a referrel code and nominal fee to get access to the vip board but it's not worth it since they removed the gold stars to be pc.
> When did this start happening? I've not had that issue (yet) but I'll look into it. > > Ugh I did notice that a while ago myself, but I thought it was a caching issue on my end. :( > >GHOUL I shall investigate.
It's a punishment from upstream. The ghost of RMS is angry that you aren't publishing recent changes to the code as free and open source software anymore.
Fake anon !ZkUt8arUCU replied with this 1 year ago, 1 day later, 6 days after the original post[^][v]#1,325,287
Ok it works now. Thank you for fixing it tteh. If it doesn't work for other people, don't worry about it. They can figure it out for themselves. The important part is resolved.
tteh !MemesToDNA replied with this 1 year ago, 1 month later, 1 month after the original post[^][v]#1,329,916
@1,324,594 (B) > Also if you then go back it used to be the new replies number was gone but now it still displays until you manually refresh.
Update: I was basically correct about this being a caching thing.
Javascript event this year, which the fora relied on to disable the browser's bfcache (back-forward cache) to ensure you'd get a fresh version of the bumps/topics page when using the back button, instead of a stale version from your browser's cache.
We also use the
Cache-Control: no-store
HTTP header, which also disables the bfcache in most browsers – but Chrome now ignores that:
> Although bfcache is not an HTTP cache, historically, when Cache-Control: no-store is set on the page resource itself (as opposed to any subresource), browsers have chosen not to store the page in bfcache so any pages using Cache-Control: no-store may not be eligible for bfcache. There is work underway to change this behavior for Chrome.
So I'm not sure if this issue is fixable. I guess I could detect when /bumps or /topics is loaded from the bfcache, and force the page to reload. Maybe that would be annoying though especially for people with slow/shitty connections.
tteh !MemesToDNA double-posted this 1 year ago, 19 minutes later, 1 month after the original post[^][v]#1,329,920
@previous (tteh !MemesToDNA) > I guess I could detect when /bumps or /topics is loaded from the bfcache, and force the page to reload.
Done. Shitty solution but it works.
> >I guess I could detect when /bumps or /topics is loaded from the bfcache, and force the page to reload. > Done. Shitty solution but it works.
If it's shitty then you should make sure it only runs this way on clients that claim to be chromium based. In this way you will not bend the knee to Google and the previous solution will continue to work on browsers that care about compatibility with web standards