Price fixing is a problem because of the power imbalance between businesses selling products, and individual consumers that need to buy them.

Worker unions are a solution to that power imbalance.

I hear ya. I know they’re not all old, and I know they are not all weird. I’m just amused that it seems that such a trite + petty label is finally rankling their jimmies because all the other labels that stunningly apply to a lot of the conservatives in office don’t seem to bother them in the least. As if … they already knew about the other ones. The MAGA conservatives waste no time slinging all sorts of generalized labels, thinking that it makes them seem stronger, but in reality, it’s just … weird.

Because they’re old, and weird.

Amoral? “Thou shall not bear false witness …” That’s one of the big ten list …

At $dayjob I switched from Apache to nginx 15+ years ago. It’s Callback/Event based process model ran circles around Apache’s pre-fork model at the time. It was very carefully developed to be secure, and even early on it had a good track record. Being able to have nginx handle static content without tying up a backend worker process was huge, and let us scale our app pretty well for the investment of time. Since then, Apache implemented threaded + Event based process models, Caddy, traefik, and a bunch of others have entered the scene.

TBH, I think the big thing nowadays is sane defaults, and better configuration, even automatically discovered configuration – traefik is my current favorite for discovering hosts in consul/Kubernetes/simple host definition files, but since traefik can’t directly serve files, I simply proxy from traefik to … nginx :)

Paige, no, no, no, no, no!

It’s uncommon for ‘public use’ ethernet ports to exist, unless they are clearly labeled. The ethernet ports might grant access to the internal network, which, is easy to accidentally do. A non-profit library with a limited budget might overlook all the extra protections on open ports (enable/disable ports as needed, use 802.11x port-based authentication, internal SSL, etc), that would be necessary to secure it. Or, even better; that RJ45 port might be wired up to an old PBX, and you may have fried their telephone system, or your own hardware.

Giulia Wylde is not amateur, but she is all those other things and more

Planka looks very promising too

TOR needs to have a lot of ‘background noise’ legit use, otherwise the folks needing to hide in the weeds stick out like a sore thumb.

You can extract the SLIC value from the ACPI table, and then pass it through to QEMU

See more details here: https://gist.github.com/Informatic/49bd034d43e054bd1d8d4fec38c305ec

It is my understanding that this can only be used to run the OEM license one one instance in a VM, on the specific hardware that is originally licensed. IE, you virtualize the license if the bootOS is Linux, but you can’t run 2 instances of the same windows license inside each other.

Because dead people in other countries don’t buy US exports.

Trump or Trump’s puppet masters?

If you use gitea, it’s just a few steps to enable it to be an OAuth2 provider. See Oauth2 Provider Docs

Not only do they not federate, they also seem to suggest they are not making the self hosting option as easy as it could be because they would prefer one instance that everyone connects with.

It seems pretty solid otherwise, and the self hosted option can work if you are willing to spar with it, but that position makes it super easy for one organization to buy or somehow influence all the primary devs and turn the project closed in no time at all.

Personally, I will use both: On servers with fixed network connections I will tend to use ifupdown; but on my linux laptops I’ll use networkmanager or networkd which tend to have nice UI’s for joining various forms of wifi networks. On my laptops for some VPN’s i"ll use the ifupdown configuration, which lets me setup all sorts of exotic configurations (bridges, vlans, vxlan, vpns, namespaces, etc.) The linux command line tooling has a litany of functions to check/test/diagnose/tweak networking settings, and they work across all the distros, AND they can reveal the full details of the network, as the kernel sees it. NetworkManager, networkd, connmann, etc, often omit details in the name of simplifying for the most common scenarios.