Projects like Arubis use a web based proof of work to slow down and and potential stop not traffic. The idea is that the proof of work makes the client spend some computer resources accessing the page so that it isn’t as computationally feasible to abuse public websites.
However, doing this all as a web service seems inefficient since there is always a performance penalty tied to web pages. My idea is what there could a special http protocol addition that would require the client to do a proof of work. Doing it at the browser/scaper level means that it would be Mich more efficient since the developer of the browser could tailor the code to the platform. It would also make it possible for bots to do it which would still allow scrapping but in a way that is less demanding on the server.
This is why I think it would be a good idea to leverage browser level code. Doing this in JavaScript is just not very efficient and if you use web assembly you are giving mobile users a disadvantage.
I’ve learned to dislike Arubis as it makes the mobile browsing experience awful
I switched to fennec and it’s basically instant. Fennec also gets ublock origin, a much better adblocker. But I’ve been too lazy to switch before this.