4 ms·
The client can just set a custom timeout and close the socket after 5 seconds of no or low activity. Then try again. On your side note; EasyList probably does
by zaarn 4y ago
The client can just set a custom timeout and close the socket after 5 seconds of no or low activity. Then try again.
On your side note; EasyList probably does not want people to start suing for starting to distribute malicious content to users (and crashing your browser on purpose is arguably malicious).
- Joel_Mckay 4y agoThere are all sorts of games people could play, as a DoS is technically an act of war under some legal systems. For example: 1. take the top 200 most popular websites in the given nuisance area 2. add ban rules to a version-B list that also includes all social media, search engines, and Wikipedia. 3. Look at the user-agent string for that specific problem client, or extreme apikey quota abuse 4. Randomly serve version-B filter list that breaks the browsing experience after a frequent update. Increase random breakage until traffic rolls off to normal levels. The TOS for the ban list file does not specify which sites it will ban, and most users will just assume it is the App that is broken (it is already). People should not do this either, even if it is also funny and relatively harmless. Also, suing people while participating in an attempted crime probably would not go well. =)
- zaarn 4y agoEven then I would not do this without clearing it with a lawyer first. You could still end up at the wrong end of a lawsuit that you'll have to defend in India.
- Joel_Mckay 4y agoThere are numerous legal/accounting specialists that protect businesses and investment decisions. We already won't serve _any_ content to IN networks as business policy... so are unlikely to ever have to visit with the cobras. Have a gloriously wonderful day =)
- zaarn 4y agoNot serving means there is already no content. That is different to serving 100TB of 404 content from clients that will never stop.