Seriously, try loading the page with NoScript, and you get nothing. Apparently, it needed nearly a megabyte of JavaScript (somehow managing to make Firefox unresponsive for a several seconds on every page load) to asynchronously load a 600 word plain text article.
Not the author's fault (apart from choosing to use Blogger), but wow, how do you fuck web design up that badly? It's just a blog, a few paragraphs and links to more articles, it doesn't need to be an entire fucking web app complete with 5 other useless ways to view a list of summaries (Pinterest is big right now, people love grids, right? Here, let me smack you in the face with this stupid zooming JQuery effect).
It's funny because "degrade gracefully" was the standard for a very long time as javascript blew up in popularity.
Now the pioneer of JS apps doesn't even bother trying to put <noscript>There is usually a blog post here if you are using javascript</noscript>
Re:GCC Poison
by AsymetricCom on Wednesday December 04, 2013 @12:14AM
(#6845162)
and I don't bother to use such sites. I think I can pass up this content.
Is this like the first time you've read a Blogger blog in years? Google mandated the Javascript nonsense quite some time ago.
Because I feel your pain, I wrote you a quick, dirty fix.
# how to fetch a blogger.com blog
# without the gratuitous javascript
# usage: nameofthisfile blog.whatever.com > html_file
#! /bin/sh
case $# in
1)
{
a=${1%%/*}
printf "%b" "GET / HTTP/1.1\r\n";
printf "Host: ${a##http://}\r\n";
printf "Connection: Close\r\n";
printf "\r\n";
} \
|nc -vv $1 80 \
|sed '
/targetBlogID/!d;
s/.*targetBlogID=//;
s/&.*//;
' \
|while read a
do
{
printf "%b" "GET /feeds/$a/posts/default HTTP/1.1\r\n";
printf "Host: www.blogger.com\r\n";
printf "Connection: Close\r\n";
printf "\r\n";
} \
|nc -vv www.blogger.com 80 \
|sed '
s/</</g;
s/>/>/g;
s/&/\&/g;
s/"/\"/g;
1i\
<br><br>
s/<name>/<br><br>name &/g;
s/<uri>/<br>uri &/g;
s/<generator>/<br>generator &/g;
s/<id>/<br>id &/g;
s/<published>/<br>published &/g;
s/<email>/<br>email &/g;
s/<title type=.text.>/<br><br>&/g;
s/<openSearch:totalResults>/<br>total results &/g;
s/<openSearch:startIndex>/<br>start index &/g;
s/<openSearch:itemsPerPage>/<br>items per page &/g;
s/<updated>/<br>updated &/g;
s/<thr:total>/<br>thr:total &/g;
s/<\/feed>/&<br><br><br>/;
'
done
;;
*)
echo usage: $0 blog.whatever.com >&2
esac
Re:GCC Poison
by PhantomGremlin on Wednesday December 04, 2013 @05:48AM
(#6846116)
Thank you very much. Your script does the trick. I was able to read the blog without enabling JavaScript for that site.
You're most welcome. What OS are you using?
While we are at it, if a site needs tweaking of noScript settings for displaying text...
Re:GCC Poison
by chrisrohlf on Tuesday December 03, 2013 @08:35PM
(#6844467)
Hi. I wrote this post and I agree with you about this particular annoyance (and apparently so do a lot of other people). Blogger themes are limited and while I can customize it I think a better solution is to move to another blogging platform.
Re:GCC Poison
by resu_nimda on Tuesday December 03, 2013 @06:46PM
(#6844051)
Did you seriously load 22kb of Google Analytics because you weren't strong enough to truly uphold your ideals? You piece of shit.
(to prevent confusion: this is a parody of the site MBlume linked)
I can't help wondering if back buttons should work differently. If you are here on this page as a result of a quick, automatic redirect and you hit "back", don't go back to the page that sent you here; skip over it to the most recent page that didn't automatically fling you forward.
Depending on the type of redirect, that is how it works.
Re:GCC Poison
by hashmymustache on Tuesday December 03, 2013 @06:08PM
(#6843872)
+1. Seriously. Is this from circular redirects? faulty browser plugin?
Can we please, please stop breaking shit that worked just fine in '95?
http://motherfuckingwebsite.com/