Hacker News new | past | comments | ask | show | jobs | submit login

That just leads to every page on the web hosting its own copy of jQuery. The whole purpose of external JS is to reduce load times by sharing cacheable libraries (admittedly with the side benefit of less bandwidth for the host).

And if you think a whitelist would work, all it takes is one look at how rapidly new JS libraries come and go to render that unfeasible




You would use content names rather than location-based identifiers in that case.


It would be really nice if we started using URIs / URNs more instead of URLs for everything, and did a better job of separating "what" from "where"




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: