4 ms·
The workarounds are reliant on filter lists to remain up to date. You can also just block websocket completely by adding the following to your filters (provide
by ryuuchin 10y ago
The workarounds are reliant on filter lists to remain up to date. You can also just block websocket completely by adding the following to your filters (provided you're not using websockets for anything else):
||*$websocket,important
You could actually use this method to create a whitelist by removing the "important" argument then creating a whitelist using the correct syntax.
- noir_lord 10y agoYep an "Off by default: This site is requesting to use WebSockets" approach would be the best solution.
- chipperyman573 10y agoThe problem is that non-techie users have started to use adblock (even my grandma had adblock on her laptop). Obviously HN users would be able to look at a page, think "Oh, a websocket could be used to provide real-time updates on vote counts" (for example), and allow it. But a regular user would see a scary warning and just close out of it.