Not really, if absent means “no change”, present means “update” and null means “delete” the three values are perfectly well defined.

For what it’s worth, Amazon and Microsoft do it like this in their IoT offerings.

Rust has perfectly fine tools to deal with such issues, namely enums. Of course that cascades through every bit of related code and is a major pain.

In the bottom picture it looks like the top “port” is just an air intake.

The option to use TOTP is already well hidden. It’s not like someone who does not know what he is looking for and uses an Authenticator already will accidentally select it.

I mean, other file sync apps upload everything to a third party while you’re working with the device.
Then, when you use another device the first one can be turned off.

How can the ISP force their dns? They can’t know where you got the destination ip from.

Not here, because it’s being used as a function argument.

That’s wrong, data is still usually encrypted.

A locked bootloader ‘just’ prevents tampering with the OS. You’re only pwned when using the phone after it has been manipulated.

Yeah I get it, it was just something I noticed. A pedantic lint, you could say.

I wanted to ask why it’s bad, what did you change?

Btw. the example function get_default is badly chosen, because unwrap_or_default exists.

That’s not how any of this works.

First of all, stripping passwords is never okay. You can reject the password and let the user choose a new one, but never just modify it on your own.

Then, if your system is at risk of code injection by certain characters in user input, please just shut it down and never turn it on again.

Stripping characters from passwords, great idea! Right up there with truncating passwords that are too long.

There is a wrapper for podman supporting compose.

But maybe it’s time to use kubernetes deployments or pods instead of compose files…

And that 20 second delay really isn’t gonna impact the trip as a whole.

That is true. Therefore there shouldn’t be a problem with drivers driving a steady speed in the middle lane.

The rightmost lane is never completely free. And if it is, almost all drivers do use it.

What makes your right to go fast on the left lane more important than their right to go a reasonable ~120km/h in the middle lane?

Okay, I never looked at a truck’s speedometer. The point is they are overtaking just slightly faster.

It certainly feels like most trucks are going at least 90 km/h regularly.

The problem is that even in low traffic, there is a truck on the right lane every few meters. Often, after you switch to the right lane, someone decides to drive right next to you, forcing you to brake.
It’s just more comfortable to stay in the middle lane.

Now IMHO the real problem is when trucks are overtaking with 101km/h…

Wow, I was sure Raspberry Pi were pretty good about mainline support, especially since multiple distros support the platform.
Software support is still very good compared to pretty much every other arm board.

Free is a loaded word and in FOSS it means “free as in freedom” as opposed to “free as in free beer”.

That’s not even free, and more importantly not free and open source.