Using a nonstandard port doesn’t get you much, especially popular nonstandard ports like 2222.

I used that port once and just as much junk traffic and ultimately regretted bothering.

I’m glad to have some competition for the Frost Oven Squoosh, which is being lightly maintained. I opened some issues in the Mazanoke issue tracker for some features to consider.

One feature I started on for that project but got stuck on was implementing a STDIN / STDOUT CLI workflow.

https://github.com/frostoven/Squoosh-with-CLI/issues/10

As I said there, the goal was a workflow where I take a screenshot, annotate it, optimize it, copy it and paste it into my blog… without creating any intermediate temp files.

At least on Linux, all the the steps of the pipeline are solved, except for a CLI image compressor that could accept an image STDIN and produce a compressed image on STDOUT.

Sounds like an oversight. Consider filing a bug with them.

https://github.com/frostoven/Squoosh-with-CLI

Nice. I use Squoosh for this, which is also free and runs in the browser.

https://squoosh.frostoven.com/

Https give you encryption in transit. The files you view will be accesible to the host.

Same idea with email.

Not true that most incoming email will plaintext. It’s the opposite:

“Most of today’s email services, including Gmail, employ transport layer security (TLS) to protect emails in transit”

Ref: https://umatechnology.org/gmails-new-encryption-can-make-email-safer-heres-why-you-should-use-it/

I have a kid about that age interested in games. There was definitely interest in social pressure to switch to Windows for gaming for the bigger selection and what friends were playing.

My experience with systemd has been the opposite. Thanks to systemd, many core tools have consistent names and CLI behaviors.

Before systemd I used sysVinit, upstart and various other tools.

I’m glad systemd alternatives exist as part of a diverse Linux ecosystem but I haven’t had a compelling reason to not use systemd.

nobody should have to deal with kubernetes when it comes to vehicle maintenance.

What mailing list features do you need?

Modern web services are served on port 443 over HTTPS with secure certificates, not on port 80 over HTTP.

Make sure you have a cert issued and installed for your server, that port 443 is not blocked by any firewall and that curl is explicitly connecting to https.

There’s no indication that running caddy in a container was a problem here.

Yes, we are waiting for the CrowdStrike aha moment where the industry learns the hard way that anticheat with root privileges was a dangerous idea not worth the risks.

For a high security context, you would want to figure out private inter-pod networking.

For what you describe, host networking sounds OK.

And: Fish implements aliases as scripts! When you use alias —save, fish creates as script with a function in it.

You could self-host Lemmy and use RSS to Lemmy services to post to your personal communities.

The opposite of VPS is more like “home lab”.

Managing a VPS yourself still counts as self-hosting.

Qutebrowser is small in market share but not in resource use.

I was scared to move the cloud for this reason. I was used to running to the server room and the KVM if things went south. If that was frozen, usually unplugging the server physically from the switch would get it calm down.

Now Amazon supports a direct console interface like KVM and you can virtually unplug virtual servers from their virtual servers too.

I started to DBAN (wipe) my internal drive once instead of an attached drive. That was the last time I ran DBAN on a machine with any drives of value plugged in.