>We noticed that you're using Internet Explorer. Polymath currently does not support this browser because compatibility issues prevent us from delivering an ideal experience. We're working on fixing these issues. People do realise that some company networks give you no control over which browser you can use right? I can't understand what feature they would need which is missing from IE10. Why not use feature detectio…
You shouldn't hotlink someone else's JavaScript
91–100 of 102 posts
Re: You shouldn't hotlink someone else's JavaScript
#92Earlier quoted context omitted.
The security risk is precisely why a lot of new services provide embeddable content via iframes now, rather than JS. On the other hand, this still isn't perfect - we wrote about it today, actually: https://www.tinfoilsecurity.com/blog/protect-your-website-fr...
As long as you host the JavaScript yourself this shouldn't be a problem. Why would it? Iframes suck.
Re: You shouldn't hotlink someone else's JavaScript
#93Earlier quoted context omitted.
One thing that will happen is that domains that get abandoned that used to host benign js will get taken over by the jerks. That's very hard to protect against, and with the rate at which start-ups encourage people to embed their tags I'm kind of surprised there hasn't been a significant incident like that.
Good point. I imagine you could make a pretty penny by hijacking credit card detail entry forms. To evade detection you can even have the hijacking code only included on pages that actually collect credit card info.
Re: You shouldn't hotlink someone else's JavaScript
#94Screenshot for potential future confused HNers when Polymath realizes it and uses a real CDN: http://i.imgur.com/A8JzHtK.png
Thank you. At first, I didn't see anything of interest and briefly wondered why I was at a site that had nothing to do with the HN subject. It hit me that the submission was to a demonstration rather than an article, so I temporarily instructed Noscript to allow all domains used by the page. Sure enough, now the banner appeared. But that speaks to another reason to not use too many scripts hosted by third-parties. It…
Not that I mind webmasters running analytics tools, but I'm concerned with google having access to too much personal data/metadata, those privacy issues are bad.
Just use piwik or something.
Re: You shouldn't hotlink someone else's JavaScript
#95Earlier quoted context omitted.
Everyone these days is so polite. OK, that was a bit of an exaggeration. But back in my day the web had a whole site high-bandwidth site specifically for educating careless webmasters about the dangers of hotlinking: g o a t s e . c x. It was used to great effect on things like auction sites where the original page html was not allowed to be changed after listing.
I'm not sure if politeness is the motivator. Imagine if you had done that, for all hotlinks to your script. Then, it turns out a children's website is hotlinking your script. Some idiot at Company X decides that it's actually your fault, since its your script that did it. To save face, they get an expensive lawyer to sue you. Next thing you know, you're a registered sex offender.
Please learn the difference between civil and criminal law.
Re: You shouldn't hotlink someone else's JavaScript
#96Re: You shouldn't hotlink someone else's JavaScript
#97Earlier quoted context omitted.
I'm not sure if politeness is the motivator. Imagine if you had done that, for all hotlinks to your script. Then, it turns out a children's website is hotlinking your script. Some idiot at Company X decides that it's actually your fault, since its your script that did it. To save face, they get an expensive lawyer to sue you. Next thing you know, you're a registered sex offender.
> To save face, they get an expensive lawyer to sue you. Next thing you know, you're a registered sex offender. Please learn the difference between civil and criminal law.
Re: You shouldn't hotlink someone else's JavaScript
#98Earlier quoted context omitted.
I'm not sure if politeness is the motivator. Imagine if you had done that, for all hotlinks to your script. Then, it turns out a children's website is hotlinking your script. Some idiot at Company X decides that it's actually your fault, since its your script that did it. To save face, they get an expensive lawyer to sue you. Next thing you know, you're a registered sex offender.
> To save face, they get an expensive lawyer to sue you. Next thing you know, you're a registered sex offender. Please learn the difference between civil and criminal law.
Re: You shouldn't hotlink someone else's JavaScript
#99Earlier quoted context omitted.
Well it just so happens that the IETF is working on the http 2.0 spec now. See https://github.com/http2/http2-spec
Yes, that is what my response was in response to. In fact I believe I link to it (not the github version but on the ietf site). However, I felt that some of the points I brought up in what I'd like to see were relevant to this discussion, even if the entire blog post isn't. This is why I highlight the points that are relevant in my comment.
Re: You shouldn't hotlink someone else's JavaScript
#100Earlier quoted context omitted.
Yes, that is what my response was in response to. In fact I believe I link to it (not the github version but on the ietf site). However, I felt that some of the points I brought up in what I'd like to see were relevant to this discussion, even if the entire blog post isn't. This is why I highlight the points that are relevant in my comment.
Sorry, what I meant was that if you think these are important features, the README.md in that git repo describes the process to get them added.