There is no RationalWiki without you. We are a small non-profit with no staff—we are hundreds of volunteers who document pseudoscience and crankery around the world every day. We will never allow ads because we must remain independent. We cannot rely on big donors with corresponding big agendas. We are not the largest website around, but we believe we play an important role in defending truth and objectivity. |
Fighting pseudoscience isn't free. We are 100% user-supported! Help and donate $5, $10, $20 or whatever you can today with ![]() ![]() |
test
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.