Hacker News Reader

Hacker News

Comment by itry | Hacker News Reader

Full thread

itry

First I had to make an account.

Then it doesnt work. Stuck at "caching page".

I hate you.

View on HN

From your profile:

> Intelligent but bad at communication. Trying to improve my communication skills.

Start by not posting "I hate you" to people on the internet.

Sorry you are having trouble with it. Sometimes the caches take a bit to generate. Please feel free to shoot us an email at help@mummify.it if your problem persists.

FYI, for those of us with Firefox's NoScript extension your site is completely broken. Nothing loads, it is just a blank page with a list of scripts you intend to run.

I wasn't curious enough about your service to whitelist your site, but I will leave a comment asking that you consider providing alternate content.

It is rare to have a site completely fail to load, even with all scripts blocked (though I accept I will have reduced functionality).

You're running an extension that purposely disables what makes the majority of the web work. Unless you disable it, you can't really complain about sites not working correctly for you.

HTML is what makes the majority of the web work, with additional functionality (optionally) provided by scripts. When I see a blank page I wouldn't call that 'not working correctly' I would call it 'not working at all'.

Maybe we agree to disagree now, and you go on blindly trusting all websites to execute random code on your machine. I am perfectly content to have new websites look a little funny the first time I visit.

"HTML is what makes the majority of the web work" - Yes, ten years ago.

The modern internet is javascript. The code is executing in a secure sandbox. If you can get it to do something random on your machine make sure to let Google know, they'll send you a pretty big check.

It's not just doing something funny with the machines, it's also doing funny stuff with other websites. Plenty of websites are still vulnerable to XSS and CSRF.

Let's hope you never need to use a screen reader.

This is a red herring. The overwhelming majority of screen readers support javascript front ends. As in, over 98% of people who use screenreaders use one that supports javascript.

source: http://webaim.org/projects/screenreadersurvey4/#javascript

Having used noscript for a while, I've gotten into the habit of letting it block everything at first and only allowing what seems necessary for that site.

I'm perfectly okay with the 'broken until enabled' model... I used to use "Request Policy" in Firefox - the most granular control of script and XSS accesses I've ever seen. Miss it in Chrome.

It's a Backbone site =p

Reply on news.ycombinator.com