@anna I guess that announcement went completely past me then! Thanks 😁

I'm not disappointed TBH, I was already trying to work out how to handle the various rooms I've bridged over the years, but if the bridge is gone I can just dump them all without ceremony.

@rwg I had blocks in the reverse proxy for hard coded user agent strings and IP ranges first. This soon did not help anymore. Presently I have deployed an anubis proof-of-work container between reverse proxy and backend service and it was really easy (I am no using any special config). I now have a tenth of the scraping requests in comparison with before, i.e. two per minute make it through to the backend whereas before it was about 20 (really very rough estimate). If scraping traffic increases again, I'll try and see how easy it is to set up iocaine.

But this all is for a backend that is not very robust and tolerant of many parallel requests. It sounds like your system, by contrast, can take a fair bit of scraping traffic. Then, I would either just not do anything or consider iocaine if I felt I just wanted to push back a bit as a matter of principle.

code4lib 2026 voting is underway!

https://docs.google.com/forms/d/e/1FAIpQLSeIOsAnmbEodwuAGoM9s_P2FcIvfOfw8fW4KojivKOu84dwFg/viewform

If you are interested in #webarchives there's a good proposal about making web archives available as static sites outside the context of complicated (and expensive) replay systems.

Replacing Legacy Sites with Low Maintenance Statically Hosted Web Archive-powered Mirrors

PS. it's not from me, honest!