RationalWiki's 2019 Fundraiser

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.

If everyone seeing this today donates $5, we will meet our goal for 2019.

Fighting pseudoscience isn't free.
We are 100% user-supported! Help and donate $5, $20 or whatever you can today with PayPal Logo.png!

Donations so far: $2900Goal: $6000

test

Jump to: navigation, search
Revision as of 14 October 2012 at 01:07.
The highlighted comment was created in this revision.

test

    -- Nx / talk edit00:51, 14 October 2012

    Did we pass?

      Sprocket J Cogswell (talk)00:53, 14 October 2012

      No. I edited my sig, and it doesn't show up on recent changes or the post's history, only on the page history, and even there it says comment text edited. At least I've discovered a way to get the original sig back (in the lqt style page history), but it's not obvious and I don't think you can get the wiki source.

        -- Nx / talk00:55, 14 October 2012

        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.

          Sprocket J Cogswell (talk)00:59, 14 October 2012

          Well, we now know the solution to the circle problem, hopefully it'll be fixed soon.

            -- Nx / talk00:59, 14 October 2012

            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.

              Sprocket J Cogswell (talk)01:03, 14 October 2012

              That's not just your computer; pre-update, I had that problem too.

                Star of David.png Radioactive afikomen Please ignore all my awful pre-2014 comments.01:04, 14 October 2012
                 

                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.

                  -- Nx / talk01:07, 14 October 2012
                   

                  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.

                    Sprocket J Cogswell (talk)01:05, 14 October 2012
                     

                    ... but that's not happening now. Big old head-scratch here.

                      Sprocket J Cogswell (talk)01:06, 14 October 2012