I like Twitter. Unfortunately every day when I log into I never know what I'm going to get. This is what I see about 50% of the time:
At first I thought it was something wrong with Twitter, which is not all that crazy given their impeccable service record *grin*. After a closer look with Firebug it's clear that the problem is on my end.
403 errors on the CSS files and jquery pretty much assure that my user experience is going to be pretty minimal.
Looking at request for screen.css we can see that the website, in this case a stylesheet resource, was blocked.
This is an error that I'm very familiar with. When I try to visit anything on Jason Bock's site I'm greeted with:
The same thing is happening with some of the backing files to the twitter site, they are being blocked.
So how can you get around this? Well Firebug allows you to edit the rendered html directly. I've found that for some reason anything from assets1.twitter.com is blocked, but anything from assets2.twitter.com or assets0.twitter.com is not.
To get twitter to work, all I had to do was change the html:
Immediately after changing the URL for the css file, firebug goes off an fetches the unblocked css file and applies it's rules, making the page look correct. Doing the same thing for the js files, behavior is once again in tact and my twitter looks normal. I'm thinking if anyone out there has any experience with GreaseMonkey (firefox plugin) you could school me real quick on how to do this automatially.
08-20-2008 8:57 AM