yarosv

from open(2):

    Note that this flag has no effect for regular files and block devices; that is, I/O operations will (briefly) block when device activity is required, regardless  of  whether O_NONBLOCK  is  set.  Since O_NONBLOCK semantics might eventually be implemented, applications should not depend upon blocking behavior when specifying this flag for regular files and block devices.

That's actually sounds way better than I expected. I went from "I want it" to "that's a potentially very expensive brick" very fast. Although it's weird that pushing image to a device on the same network has to go through your servers.

Not sure about him, my use case is the piece of hardware I can buy without being afraid of your company dying and shutting down servers or my internet not working.

I'm not trying to be aggressive here. But what's the actual end user difference between NAT and firewalled ipv6 for me and my local network then? I assume I could route now than one addresses for a specific port. On the other hand I have to pay for domain record to access my local resource without a struggle.

Should I use ipv6 at home when my doesn't have one?

I honestly struggle to find good information on the protocol that's decades old. It's either to deep for me to care for my needs or too shallow to understand why and how should I just it. Scaremongering is what I find on the internet. And no real benefits for me to update my hardware or find ISP that has ipv6.

I'm not a network engineer. But I've yet to see a good way to protect ipv6 network. I don't want my local webserver develop on to be exposed to the internet. It's my understanding that default router configuration will do just that. I don't see a good way to deal with privacy issues. Ipv6 essentially gives a unique identifier for every computer in the household by default.

Is synaptic not a thing anymore? I haven't used linux in a number of years.

I don't feel like it. Looks like more of an explanation so people don't feel weird when they see Domain Privacy instead of WhoisGuard in the renewal screen.

And when the server goes down, all the motors turn into e-waste

Sure, what bothers me is how inconsistent it is. Function parameter of type Template is `t` but local variable of type Template is `tmpl`.