We are the goon squad and we're coming to town, beep beep.
Fuck Blogger.
I had a lovely, long, funny, well-written post about the Will Danger Family Values Tour '05, Montana... but Blogger fucking ate it. It was all done, about 45 minutes after signing into Blogger, and I pressed "Publish" and it disappeared, with a prompt to sign in to Blogger again. It would not let me retrieve the post. Cocktoasters. This has happened to me four or five times on different occasions. Apparently, you have to re-log in to Blogger after 45 minutes. We must watch out for Blog-jackers, who tip-toe into your computer room while you are taking a leak and "tag" your blog with grafitti. Sounds like an issue of homeland security, you know.
Shit. I just don't have the heart or mental energy to re-write it from scratch.
Anyone else have this problem? Anyone know how to avoid this?
I will give it another whirl tonight maybe. And keep an eye out for blog-jacking gnomes, and the Blogger Homeland Security Team.
CODE MAUVE!!! CODE MAUVE!!!!!!!!!
I had a lovely, long, funny, well-written post about the Will Danger Family Values Tour '05, Montana... but Blogger fucking ate it. It was all done, about 45 minutes after signing into Blogger, and I pressed "Publish" and it disappeared, with a prompt to sign in to Blogger again. It would not let me retrieve the post. Cocktoasters. This has happened to me four or five times on different occasions. Apparently, you have to re-log in to Blogger after 45 minutes. We must watch out for Blog-jackers, who tip-toe into your computer room while you are taking a leak and "tag" your blog with grafitti. Sounds like an issue of homeland security, you know.
Shit. I just don't have the heart or mental energy to re-write it from scratch.
Anyone else have this problem? Anyone know how to avoid this?
I will give it another whirl tonight maybe. And keep an eye out for blog-jacking gnomes, and the Blogger Homeland Security Team.
CODE MAUVE!!! CODE MAUVE!!!!!!!!!
posted by Joe at
12:22 PM
3 Comments:
The trick is to highlight your post, and copy it (Control+C) before clicking publish. The reason why this happens is because the "flow" which contains your TCP handshake between your machine and blogger times out after a certain length of time. typically a high traffic site has a load balancing mechanism between multiple servers with the same content. This load balancing mechanism keeps track of you through a "flow" which maps your IP address to a single server. However, it's limited in the amount of resources it has and a timeout for flows is specified for good reason. If there wasn't a timeout, server (blogger) resources could be consumed without something to keep it in check. Then, none of us could blog =(.
Oh, to add on.. If your rant does get lost, it's still in your buffer, so just paste it. Your probably savvy enought that i need not have explained this -- but it was just for the sake of being thorough. ;)
gotta love the technical detail of an engineer. makes accountants look practically aloof.
Post a Comment
Subscribe to Post Comments [Atom]
<< Home