Oh, well... I'm not bothered. While I'm still getting a pulsing circle while typing this, the whole LQT experience seems to be proceeding at an acceptable pace, much more lively than before.
Well, we now know the solution to the circle problem, hopefully it'll be fixed soon.
Aargh. Refreshing the page in ancient firefox on antique fedora causes the most recent thread to disappear. That's another one of the reasons I've been avoiding talk pages with LQT.
Carry on, you're far better equipped to deal with this than most of us, I suspect.
That's not just your computer; pre-update, I had that problem too.
Oh, THAT bug. It's actually not caused by your browser, it's caused by LQT being stupid. You see, when you add a comment, a thread gets bumped, which means its last modified timestamp is updated. But when you click on a link in recent changes, that link has a timestamp in it, and it only displays threads before that timestamp. But the thread you were trying to get to now has a newer timestamp, so it disappears. In your case, the url you refreshed probably contained a timestamp (the offset= part), and when you refreshed, the thread disappeared because I bumped it.
I also notice that visiting an LQT page often lights up my system monitor, indicating that some script may be hogging cycles on me local machine.