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 has strong Alfur energy.

I’ve been using Linux for 25 years. I started with SuSe, switched to RedHat after a couple months, and after a few more months switched to Gentoo… for 10 years, then did Arch for the remainder.

Frankly, I think that distro hopping is a bad idea because it means you don’t get enough time really understanding how to fix things. As a long time Arch user, it would never occur to me to throw out 10+years of tooling and scripts, muscle memory and shorthand to fix a driver issue. I would read the wiki top to bottom and then go spelunking through other sources until I find the solution (then update the wiki) before I’d switch to something foreign with its own set of problems and unknowns.

My advice is to find a distro that makes sense to you, and that has a deployment pattern you like and commit to it for a few years. Don’t switch unless you find something that fulfills those two requirements even better, and even then do so cautiously. Your experience and understanding is hard-won.

Ooh! I have something for this.

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?

Also Ctrl+D to exit any shell and Ctrl+R for reverse searching your history!

Just be careful with files with spaces in the name. There’s an incantation with xargs that I always have to look up when I want to use it safely.

Not in and of itself, but I find that I have a handful of common tricks that I can put into aliases. Also, there’s ffmpeg.app!

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.

I’ve used Starship before, and while it’s quite powerful for formatting what goes into your prompt, I don’t believe there’s any feature in there that will fix the prompt to the top of the screen. The best I could find in the docs was a feature to place some text to the right.

Yes, that’s it exactly.

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.

Hear me out: I want the prompt at the top of the screen.

It’s terribly inconvenient to have the place you’re typping your command into at the bottom. On laptops, your fingers are in the way, and on desktops, you’re always craning your neck looking at the bottom-left.

Imagine instead if your terminal looked like this:

| ---------------------------------------------------------------------------- |
| $ curl https://...
| ---------------------------------------------------------------------------- |
| $ echo "hello"
| hello
| $ ls
| output.png
| goes.txt
| here.webm
| ---------------------------------------------------------------------------- |

After a command is entered in the upper pane, it’s appended to the lower pane along with the output just like a normal terminal. Maybe even something like translating Shift+Enter to mean “clear the output pane and run”.

Could Wine help out here?

What is the deal with getting gpu acceleration into a terminal emulator of all things? Of all the innovations that we could use, faster drawing of text doesn’t feel like it should be a priority.

This is an excellent idea. Fortunately you’re not the first to have it ;-)

You should look into alias.

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.

How do you test for lead though?

How the hell do I find cinnamon that didn’t have lead in it?