Are these Firefox bugs, or are they Twitter ones?

We all know certain computer bugs only seem to happen to me, as I have chronicled frequently. Yesterday, we had a router fault. Today, my desktop machine refused to recognize my hard drive. And now, using Twitter, I notice that the type has gone monster-large:

   This has happened twice today. I did not hit Firefox’s enlarge function (impossible to do so “accidentally” on my laptop, without a numeric keypad), which would typically enlarge the background as well. You’ll also notice that the ‘Latest’ paragraph is in the correct point size. Has Twitter been fiddling around with its stylesheet, or did I stumble across a “large type” version of the site?
   I also managed to get search.twitter.com returning 404s today as my other accomplishment. I wonder if anyone else can see this page. I cannot—but it’s a simple, routine search for an earlier Tweet of mine. It seems I managed to break Twitter Search just by using its features (feeding in keyword, username and a date range). I believe others will get a 404 with the above link, too—which I think should dispel the growing myth among my friends that I have the worst luck with computers. Use them regularly enough, and you will break websites, programs and hardware, too.
   Meanwhile, PHP in Autocade prompted me (and no one else I asked to test this) to save a page, rather than open it, at different times today (see below). (This only began happening since Firefox “upgraded” to 3.0.11.) Again, this was unique to me, on both Windows Vista and Windows XP, though I believe the fault lies with the browser: One of my Twitter friends suspects it is advertising code, which is possible, since I managed to get this page working at other times today. However, it still begs the question: why just this one page, when the coding for the CSS and other elements to the page is identical to the rest of the site? And why does Firefox not want to open a page that is encoded ‘application/opensearchdescription+xml’, which I know is compatible with it?

PS.: Fellow Tweeter Ajay reports he experiences the first error.—JY