Due to the nature of critical infrastructure it would not be advisable to force lockout rules and rate limiting on devices.
The main issue comes from the long life cycle of equipment and companies not wanting to change to new securer methods due to fear of costs implementing it.
AFAIK: U-Block Origin is a fork of U-Block which hopes to stay in sync with U-Block, but maintain a per-site block/allow feature which was removed from the newer version of U-Block.
I'm curious to know what will happen with all the user data on their systems. There was a site floating around which allowed you to access your playlist information just by entering your account email. I assume that was old public data.
And with services like this, is there any threat to users who access 'illegal' material?
Look into R+D. I was in the same boat as you. Then I decided to take a look at research, now can't get enough of it. There are government funding for PhD's (Search Department of Education and learning (DEL) Funding.)
The creative commons site provides links to popular search engines with with Create Commons licenses. Though these are not Clip art, there is a lot of material which you can use. Just needs a bit of searching.
It's all well and good adding support for new algorithms, and streamlining the UI. But still, access to the key servers are done over plaintext[1]. Which could allow an attacker to modify your request/response from the keyservers.
Am I correct in believing that this is a critical issue not to address?
[1] "Support for keyserver access over TLS is currently not available but will be added with one of the next point releases. " -- https://gnupg.org/faq/whats-new-in-2.1.html
The main issue comes from the long life cycle of equipment and companies not wanting to change to new securer methods due to fear of costs implementing it.