3 ms·

Easylist should serve the Indian browser (based on user-agent) with a giant file (expensive), a corrupt file, or some response which causes the app the crash. I

by ff7c11 4y ago

Easylist should serve the Indian browser (based on user-agent) with a giant file (expensive), a corrupt file, or some response which causes the app the crash. If the browser crashes on every startup due to a malicious response from the Easylist server, users will likely delete it.

paxys 4y ago
Serving a giant file is going to affect their servers more than the end device. If they could identify the user agent it would be a lot easier to just block it entirely.
- zamalek 4y ago
  Could be done with a gzip bomb.
  - jefftk 4y ago
    Or a brotli bomb, for far greater expansion!
    - wink 4y ago
      And a terrible idea because the users are not at fault, but the developers of the app. And in this case it might crash so they'd only report "app crashes on startup", if at all.
angch 4y ago
Just a separate rules file that blocks .in and other popular domains for India will probably work just as well.
aembleton 4y ago
Then the browser could just pretend it is Chrome (if it isn't already) and that would easily work around your solution. I think something like this would be best served by moving to IPFS or Bittorrent. A magnet link could be provided and then browsers and plugins could use that to download the file. That way, you can distribute the load.
sinuhe69 4y ago
No, a file with a single line: “11) You should not download the list by every start” is enough