TPM is great on paper, but in practice, there was little planning to ensure that cryptographic keys would be safeguarded by hardware manufacturers, and that’s exactly what happened. Now TPM is considered weak as a means of securing data.

https://www.tomshardware.com/software/security-software/secure-boot-key-compromised-in-2022-is-still-in-use-in-over-200-models

Wow, armv7 is definitely back there in terms of support. One of the more known v7 devices was the nexus 7, released in 2012.

Makes sense. Your 2nd definition is what I take from the term scaling. Let’s see if op comes back with any notes.

For video encoding, I run an 8th gen Intel i5 8500t. The quicksync is good enough for nearly anything 1080p.

Not sure what you mean by the “scaling”.

Nice work. I would read more articles like these.

“Pleb” is generally used as a pejorative and is roughly equivalent to calling someone a peasant.

Are you not using LE certbot to handle renewals? I can’t even imagine doing this manually.

Except Debian packages do get very old.

Except nothing. Not the point. You are taking this way too seriously. I’m not disrespecting arch, it’s a joke.

Arch users… Every. Single. Time.

Listen, if Debian users can take all the “Debian==old and bad” flak, you can handle a little ribbing about arch.

I don’t know… I’m skeptical of its bandwidth.

OK,fair enough.

mdns (multicast DNS ) is specifically designed to work where a DNS server is presumed to not know hostnames, usually on a local network. So it is possible to use hostnames without a DNS server.

On fedora, discoverability of mdns should be on by default. Configuring mdns presence to others is a config away, if not enabled by default.

I love alpine, and I use it where I can. And it has many advantages over other distros and setups. But a declarative, ram-only distro that boots over the network doesn’t help manage non-conformant machines.

I still need to manage Debian, old centos boxes, Ubuntu machines, and a couple old-as-time sun machines. Nixos isn’t the tool for that job. Ansible has two dependencies: ssh and python, and there are ways around the 2nd one. Ansible works really well here.

Not trying to bash nixos, here, but I’m not sure why so many users on Lemmy compare ansible and nix, they don’t really operate in the same spaces.

Can you manage a Debian server with nix?

Hahaha nice. I have PTSD from teaching the interns how to search graylog and then locking up elastic with piped conditional searches.

I appreciate the response.

I’m still keeping an eye on these technologies and I hope we can set some decent standards for alternates to WiFi and LTE narrow band.

I’ve been watching halow for a while, I haven’t yet seen any sustainable, real-world examples beyond a few hundred kbps (not bytes). I have seen the 1Mbps results, and they’re promising, but most places with any other traffic in the free band is busy. If you have any successful and repeatable tests hitting at usable speeds, I’d love to see them.

After getting into meshtastic and a few other lorawan projects, I’m a bit concerned that tests for these are always high and visible, which doesn’t work well in the mountains, even at shorter ranges.

I used to be more hands-on with these new standards, but I’ll wait for better tests to come from halow before I try it out.

Definitely possible, and there is already some tech with the kinks worked out like wimax that could wirelessly serve a whole town. There are also folks who have created their own isps to fill in where the big players don’t bother. It is apparently regulatory hell to get up and running.

The problem isn’t technology, it’s people.

Like every protocol in the unlicensed 900mhz range, 802.11ah has a very limited transmission rate in the 50 to 100 kbps range.good for occasional data like sensors or a few bytes of message, but not for any modern comma like AV, mass file transfer, etc.

If you’re not fond of manipulating config files manually, just use nmcli (from your link):

You can get an idea of NetworkManager’s settings by running nmcli on the command line.

It is a bunch simpler. The days of just raw-dogging resolve.conf and nsswitch are long behind us.

Aren’t these docs an admission that it’s a clusterfuck?

The Debian wiki admittedly needs work, but it is a wiki, so make an account and update what you think is lacking or unclear.