Today we enabled Cloudflare CDN on the project and website. This provides a few advantages for us, the most important being content caching to take some of the burden off the server's network connection and instead cache the large client and dataset downloads across the Cloudflare CDN. At least in theory. This also has the benefit of providing traffic monitoring and things like DDoS protection if for some reason such things should happen.

Nothing should change from the user perspective! So if something on this website or the project stops working, please post the issue here.

This step is necessary to help the project handle a larger number of users in the future.

So far things seem to be going pretty well, we're saving a ton of bandwidth, and we've had reports of client app downloads going orders of magnitude faster.

One thing we noticed, legitimate requests from the user agent "python-urllib' are by default blocked by the CDN. We just rolled out a change to fix this, so hopefully, people writing homemade scripts to query the site will no longer be blocked.

If anyone else notices any similar issues, please post them here.

Hi:

Do you mind letting through curl/7.54.1 as I am graphing the server_status page, and unfortunately cloudflare has blocked the default LWP::UserAgent agent. Or alternatively can you unblock libwww-perl/6.35

These are the statistics I graph:
https://munin.kiska.pw/munin/Munin-Node/Munin-Node/results_mlcathome.html
https://munin.kiska.pw/munin/Munin-Node/Munin-Node/transitioner_mlcathome.html
https://munin.kiska.pw/munin/Munin-Node/Munin-Node/workunits_mlcathome.html

I'll see what I can do when I get back in front of a computer.

Sorry it took me a few days (holidays and all) but this should be allowed now too. Thanks for reporting!