October 27, 2006

Have you been having trouble seeing new posts to this blog?

I had that problem myself in Firefox, and it's corrected in this new update. For some reason, the "check for updates" function in Firefox was not showing that this new version is available. It is! Update! And see the constant refreshment of Althouse!

CORRECTION: It's Firefox, not Foxfire. I wonder how many other syllables I've been reversing without putting myself in a position to attract corrections. Foxfire is bioluminescent fungus, you know.

MOREOVER: In the episode of "Lassie" that first aired on October 26, 1958, "Timmy and Boomer hunt foxfire to smear on their faces and become trapped in an abandoned house in the woods that is scheduled for demolition." Reason for wanting to smear luminescent fungus on their faces: to scare the girls out of kissing them at Martha Tyson's Halloween party.

25 comments:

Anonymous said...

Firefox?

Anonymous said...

I use IE and have been getting Intenal Server Error 505 messages lately -- but just with Althouse, no other Blogger sites.

dave said...
This comment has been removed by a blog administrator.
Anonymous said...

Dave: A complete TOOL on the internet.

Grow up and learn to be polite.

Edward said...

Ann: Yes, I actually did have problems with updates to your blog not appearing within Firefox.

Refreshing the page one or two times would usually make the updates appear, but they would not appear as early as they should.

AND, I’m already using the latest version of Firefox, which means the problem still happens even with the latest version.

The problem has not been burdensome for me, because I usually keep IE and Opera open at the same time with Firefox. I find certain web pages work better with different browsers, so I’m often jumping from one browser to another.

I would recommend to everyone to download and use both Firefox and Opera.

The Internal Server Error 505 message has been periodically shutting down all the blogs hosted by Blogspot over the past few days. I think the increased traffic due to the upcoming election has overburdened the servers hosting Blogspot.

Ann Althouse said...

Thanks for the correction!

Edward: Check again and make sure you have the newest newest version.

Dave said...

Firefox sucks up RAM. But it is better than IE.

Juliet said...

Thanks! I didn't know there was a new version. I think the auto-refresh is working!

Ann Althouse said...

And Edward, go to the link Gerry gives. The update within the program will wrongly make you think you have the current update.

Ann Althouse said...

I mean the link I give in this post. (Gerry provided it in the comments on another post.)

Mortimer Brezny said...

It is also an anticlimactic film with an experimental jet fighter pilot played by Clint Eastwood.

bill said...

It is also an anticlimactic film with an experimental jet fighter pilot played by Clint Eastwood.

...whose jet fighter chase scenes are early examples of CGI and would often be shown on the screens at 1st Avenue (Mpls) as background for early 80s Eurotrash dance music. Various scenes from Tron were also popular.

Alan said...

As a Mac newbie (MacBook since May), I don't think I could give up using Safari. I love the built in Dictionary. All you have to do is right click a word and select Dictionary....or highlight a word and hit CTRL+Command+'d' and the definition pops up a little balloon box. This is my favorite Mac feature.

Cindy said...

Foxfire was the name of a popular set of back-to-the-land how-to books in the 60's and 70's. I have been using Firefox for several years and I still have to stop and think whether I have the syllables in the right order. Glad to know I'm in good company!

Also, thanks for the update link.

Anonymous said...

Cindy --

The Foxfire Book (Anchor Books, 1972): Hog dressing, log cabin building, mountain crafts and foods, planting by the signs, snake lore, hunting tales, faith healing, moonshining, and other affirs of plain living.

Softcover. 384 pp. $3.95

bill said...

The Bioluminescence FAQ

rightwingprof said...

Actually, it's not Firefox. It's blogger. Blogger, for some reason, does not have the necessary code to prevent the browser from caching the page. It's not just you. It's every site on blogger.

rightwingprof said...

I first noticed this on September 4.

Anthony said...

There are also several bioluminescent species of jellyfish and other creatures inhabiting the waters around Puget Sound. You can also smear jellyfish on your face for the same effect.

And swimming in bioluminescent water (er, um, actually skinnydipping, but hardly erotic since the water is coooooold) is like swimming in fireworks. I heartily recommend it. Once.

Gerry said...

Rightwingprof, that is not quite right.

The standards (RFCs) for browser behavior state certain approaches which are to be taken when determining how long to cache a page when the server does not return a specific time for when the page expires. The 1.5 version of Firefox had a few different bugs which caused the behavior Ann was experiencing (and you noted). The most significant was when the Last Modified Date header was actually in the future-- something that Blogger occasionally returns due to the time on one or more of their servers being incorrect. When this would happen, Firefox would cache the page with an expires date many years in the future (you could see this screwed up expires date if you chose Page Info from the Tools menu when the page was not refreshing).

If you upgrade to Firefox 2.0, you will no longer see this problem. I coded this patch myself! :-)

Gerry said...

Ah, what the heck. I'll get long winded and explain further.

Per the RFC, caching can be done via heuristics when the "Expires" header is not specifically set the the server. The way Firefox implemented the RFC was to look at the LastModified header. The further it was in the past, the longer the page would be cached (with the logic being that if the page had not been modified in a long time, then it could probably be cached for a long time without there being much risk of fresh updates to the page being missed).

Well, the bug I described above was such that this calculation was screwed up when the CurrentDate as returned by the server was earlier than the ModifiedDate returned by the server-- something Blogger occasionally does (Blogger always returns the current date as the ModifiedDate as a way to prevent caching, but for some reason sometimes it would have that be a few moments later than the CurrentDate). The calculation Firefox did in this case would result in strange things such as setting the Expires date to June 7, 2020.

Theo Boehm said...

Alan: Safari is indeed fast, slick, and nicely integrated into the Mac OS. I used to love it.

However, you'll find Firefox has a richness of features and customization possibilities that Safari simply can't touch. Firefox with the "Performancing" extension, for example, is incredibly helpful for blogging or commenting.

The ability to customize the user interface is a real plus as well. You can make Firefox look just like Safari or IE, or anything in between or something entriely different.

Firefox 2.0 for Mac is very, very nice. Kudos to Gerry and the entire Mozilla/Firefox community.

Revenant said...

Foxfire was the name of a popular set of back-to-the-land how-to books in the 60's and 70's.

More importantly, it was also a movie in which Angelina Jolie gets naked.

rightwingprof said...

Ah. But it was, as I observed, a blogger problem.

I plan to upgrade to 2.0 when all of my extensions -- well, at least the ones I use every day, like the web developer extension -- run on it. I've been refreshing the page every time I've hit a blogger site for two months, and I'd rather continue to do that for a while than do without my extensions.

Gerry said...

"Kudos to Gerry and the entire Mozilla/Firefox community."

Theo, you are welcome, although I hardly am part of that community in any meaningful way. I am a computer programmer, who took advantage of the open-source architecture to look and find why a single annoyance was occurring. Out of the millions of line of code in Firefox and the Mozilla suite, I have about 10 lines.

It felt pretty neat, though, to have the 'real' Mozilla programmers say "his patch looks good to me."