It's a rather brilliant idea really, but when you consider the environmental implications of forcing web requests to ensure proof of work to function, this effectively burns a more coal for every site that implements it.
Sure, but what you "get done" on your own is statistically irrelevant. To achieve useful, measurable success in the fight against climate change, collective action must be taken at scale. That's government.
This is pretty slick, but doesn't this just mean the bots hammer your server looping forever? How much processing do you do of those forms for example?
You might be interested in this project where someone has hooked up a low-power system to Mastodon and is tooting through it stories about the experience. The project author may also be worth contacting.
What exactly are you self-hosting that's gobbling up that much data? I've been self-hosting my website for decades and haven't used that much over all that time let alone in one month.
Most of my bandwidth consumption is from torrents and downloading Steam games, but even that doesn't get me to even 1tb/month.
So long as politicians are all painted with the same negative brush, there's no room for anyone with a genuine interest in improving things. There are some truly great, caring people in politics working hard to do the right thing. It's not their fault the public keeps voting for assholes.
You can't really make them go idle, save by restarting them with a do-nothing command like tail -f /dev/null. What you probably want to do is scale a service down to 0. This leaves the declaration that you want to have an image deployed as a container, "but for right now, don't stand any containers up".
If you're running a Kubernetes cluster, then this is pretty straightforward: just edit the deployment config for the service in question to set scale: 0. If you're using Docker Compose, I believe the value to set is called replicas and the default is 1.
As for a limit to the number of running containers, I don't think it exists unless you're running an orchestrator like AWS EKS that sets an artificial limit of... 15 per node? I think? Generally you're limited only by the resources availabale, which means it's a good idea to make sure that you're setting limits on the amount of RAM/CPU a container can use.
The source looks like https://linktr.ee/massesutd though the dude doesn't appear to have a website, just links to a bunch of gated websites that I can't access without an account.
I guess it's been a while then. Syncthing works perfectly for me, with the official latest version in Arch, the older version in Debian, the flatpak on Ubuntu, and the forked version on Android, syncing all my Joplin data all over the place.
I don't much care for the file format though. The appeal of Git Journal is strong.
It was Castlevania that did this to me.