4 ms·

I started reading this thinking what a complete dick but on reflection they are right. It's as hard to show a feature list and ask to be white listed as it is t

I started reading this thinking what a complete dick but on reflection they are right. It's as hard to show a feature list and ask to be white listed as it is to redirect to http://www.enable-javascript.com/ http://www.enable-javascript.com/. Well said. Thank you.

drostie 15y ago
There is perhaps a lesson here. Hopkins said it this way[1]: Each mortal thing does one thing and the same: Deals out that being indoors each one dwells ...and he then calls for humanity to rise above this standard case. It is functional, if sub-optimal[2], for how we can organize society: every single person complains about what bugs them, and we connect the social graph dynamically to make people happier -- the people who want a NoScript user's business will design with them in mind, the people who don't care enough, won't. I would add that this applies not just to JavaScript but also to cookies. We use NoScript and Cookie Monster because they're condoms for the Internet -- they protect us from tracking cookies and some XSS attacks. The web site for Priv.ly unfortunately breaks when you use NoScript. The reason for the break is to make four links appear when you mouse over an image which is hiding them, and then those links load videos into that element. Basically, the element is an iframe for videos, except they didn't use an iframe. It would have been faster to develop if they had just used an iframe to load their videos, and then their videos could probably be covered by a NoScript exception for Vimeo. If the site didn't break, it would say, "You do not have scripts enabled, which means you are either running old technology, or are our kind of person. If you are the latter, we hope you will consider helping out." This is almost very nice and polite -- but please, skip the crap about "running old technology" when you follow-up on this example, and instead just condense the content which you were going to show me into a short summary with a nice little end point, "to see my app, please enable JavaScript." If your app is its own summary, like a blog article, then you absolutely should not require JS to display it. [1]: http://www.bartleby.com/122/34.html http://www.bartleby.com/122/34.html "As Kingfishers Catch Fire" [2]: http://www.ted.com/talks/lang/en/david_logan_on_tribal_leadership.html http://www.ted.com/talks/lang/en/david_logan_on_tribal_leade... "Different Stages of Tribes"

drostie 15y ago

There is perhaps a lesson here. Hopkins said it this way[1]: Each mortal thing does one thing and the same: Deals out that being indoors each one dwells ...and he then calls for humanity to rise above this standard case. It is functional, if sub-optimal[2], for how we can organize society: every single person complains about what bugs them, and we connect the social graph dynamically to make people happier -- the people who want a NoScript user's business will design with them in mind, the people who don't care enough, won't. I would add that this applies not just to JavaScript but also to cookies. We use NoScript and Cookie Monster because they're condoms for the Internet -- they protect us from tracking cookies and some XSS attacks. The web site for Priv.ly unfortunately breaks when you use NoScript. The reason for the break is to make four links appear when you mouse over an image which is hiding them, and then those links load videos into that element. Basically, the element is an iframe for videos, except they didn't use an iframe. It would have been faster to develop if they had just used an iframe to load their videos, and then their videos could probably be covered by a NoScript exception for Vimeo. If the site didn't break, it would say, "You do not have scripts enabled, which means you are either running old technology, or are our kind of person. If you are the latter, we hope you will consider helping out." This is almost very nice and polite -- but please, skip the crap about "running old technology" when you follow-up on this example, and instead just condense the content which you were going to show me into a short summary with a nice little end point, "to see my app, please enable JavaScript." If your app is its own summary, like a blog article, then you absolutely should not require JS to display it. [1]: http://www.bartleby.com/122/34.html http://www.bartleby.com/122/34.html "As Kingfishers Catch Fire" [2]: http://www.ted.com/talks/lang/en/david_logan_on_tribal_leadership.html http://www.ted.com/talks/lang/en/david_logan_on_tribal_leade... "Different Stages of Tribes"