40 ms·
Yet another reason blindly running javascript from unknown parties is a bad idea. Whitelists for progressive enhancement I want should always have been the defa
by prodigal_erik 14y ago
Yet another reason blindly running javascript from unknown parties is a bad idea. Whitelists for progressive enhancement I want should always have been the default.
- danielweber 14y agoIf the ISP is injecting Javascript, they can just inject it as coming from the same domain. I don't like "force HTTPS everywhere" but these jerks are forcing it. It sucks, but it sucks less than this.
- begurken 14y agoI advise meditating on 'force HTTPS everywhere' for a little while. The idea has a great number of pros, and almost no cons. In general, leaking information to intermediate parties about what you're doing is bad, because they can use it against you, even if you have nothing to hide. At least with SSL, they only know the sites you're visiting, and can't see or fiddle with the content.
- codesuela 14y ago@begurken you've been hellbanned since this post https://news.ycombinator.com/item?id=5466310 https://news.ycombinator.com/item?id=5466310, no idea why https://en.wikipedia.org/wiki/Hellbanning https://en.wikipedia.org/wiki/Hellbanning
- danielweber 14y ago> The idea has a great number of pros, and almost no cons. 1. Certificate problems with embedded devices. 2. Much harder to control what's going on with your network.