IME most of the time this kind of thing isn't really about control, it's about liability (at least in the corporate world).
If a company contracts an external provider to handle endpoint protection, veeps who know nothing about IT get to tick their "all practicable steps to protect customer data" and "certified industry standard solution" boxes. If anything goes wrong they can just point at (and potentially sue) $external provider, with no risk of blowback.
The bigger and more widely known the provider, the harder they can lean on the "industry standard" "we're doing what everyone else is doing" angle.

This is how we end up here, not because of some grand conspiracy (not to say they're not out to get you, mind) but because big IT knows they can exploit human laziness and risk-aversion for profit, and their corporate customers often like dealing with a monopoly because of the "safety in numbers" effect.

As for "cloud" more generally, my answer (both personally and professionally) is "go away"... Unless the rep brought biscuits, in which case I'll pretend to listen while I eat them*. It simply does not and can not meet my reliability, serviceability and redundancy requirements.

I don't like surprises, and if I really do need to call somebody at 3am to figure out why a critical system isn't working, I expect the answer to be "I'll be on site, with parts, in 30 minutes" not some phone droid with "looks like $cloud whatever is down, better file a ticket".
'tis the same reason I prefer hardware solutions over inscrutable software "fixes", and local contractors over megacorps with 15 layers of bumbling bureaucracy between their technicians and reality.

*the biscuits, not the rep... Though the reverse is often tempting.

As far as I can see, yeah.
i.e. a bunch of whining because copy-pasting commands without understanding what they do or checking the result doesn't work on Devuan...
Apparently needing to change the distro name yourself rather than being spoon-fed an inline if statement makes for "frustration times a million" and the mullvad folks "bumbling morons".

(emphasis mine) One anecdotal sample is barely a "test" at all, and not even remotely scientific.
Then you go on to claim that blind tests have problems, because the usual "bit-perfect" "exclusive mode" audiophool nonsense.

As for "old theory", I've been there, done that, (as well as built and tested plenty of proper HiFi gear) so I'm no longer gullible enough to get sucked into such arguments... I'm out of here, have fun.

Shiny New Shit
Embrace, Extend, Extinguish

As for FOSS and systemd... systemd is FOSS, and while I don't particularly agree with the design or the attitude of the designer(s), that's not really what I was referring to.

For people running proprietary black-box systems... Which is, at least for the most part, not us.

Video summary: Windows bad, Apple bad, Google bad, AI bad, everyone and their dog wants endpoint control and uses FUD and "think of the children" to get it.
IOW, corporate big-tech abuses their power and their users, and normies just don't care because herd-mentality and convenience. Same old, same old. *yawn*

All this really does is incentivise me to avoid buying SNS hardware (instead donating further to the FSF), and keep a weather eye on FreeBSD and OpenRISC in preparation for the day GNU/Linux finally falls to Microsoft EEE and the horde of clueless ex-windows users pushing non-FOSS software and non-FOSS attitudes.

If they have a path to the internet at large, which they won't if you properly secure your wireless AP.
They could of course come with a cell modem, but that's relatively expensive and would require cooperation from a cellular carrier. Manufacturers of two-bit crap don't like to spend any more than they need to, and the reason many devices have onboard wifi is that it costs nothing because it's built into the SoC they're using.

The real solution of course is not to purchase IoT garbage to begin with, such things tend to be bottom-dollar never-patched security nightmares even on a good day.

Yes yes, old news, such toys already exist (microphone included). Don't allow them to connect to your wireless (infrastructure), and don't have devices around that mindlessly try to connect to open networks in general (ad-hoc). Better yet, don't buy them to begin with.

Nobody makes talking teddy bears or "smart" toasters internet capable to spy on you, they do it because "cloud" is the cheapest possible way to implement the features they think will sell more units or because it allows them to milk you for some kind of subscription service.
The most effective thing you can do about this practice is to vote with your wallet and not buy such things.

Riiiight. Who exactly do you think is noticing your "protest"? The same people whose "eyes" you are "opening" with constant whining and opining that "somebody" needs to do "something" about [childish adjective of the day] "evil" corporation?

Buying an off-the-shelf router and installing openwrt on it isn't protesting, the manufacturer made a sale and that's all they care about.
If you want to protest, go organise a protest.

If you ask me, the relentless ill-informed tinfoil-hat noise on this board is the biggest problem with Devuan right now. It's leading the wider community to view the whole distro as a "fringe OS for conspiracy theorists", and people are laughing at us. Please stop already, it's embarrassing.

Sure:

root@apollo-slink:~# apt install apt-transport-https
bash: apt: command not found

'apt-get' does exist, but as it's name implies it only works when "getting" packages from the repositories.

Yes. The wget and apt commands share CWD, so an intervening 'cd' is redundant unless you explicitly tell wget to drop the file somewhere else.

Also what fsmithred said. Installing from a local file with apt is relatively new and may not be available everywhere. Dpkg will be.

Uhh, what on earth does your router OS or wireless chipset have to do with any of this?
If you think a router or firewall is going to do anything useful about the data harvesting that goes on on the modern garbage fire internet, think again.
Blocking advertisements (whether at the router, on the client machine, or in your browser), does exactly what it says on the tin and no more. Ads are indeed a privacy concern, but they're only one of many.

Really? We need to drag brain-rot politics in here too?

Careful, whining about whining about politics is still whining about politics.

OTOH, maybe if we derail this thread hard enough it will spontaneously combust. Once the stinky smoke clears, I expect that'll be a relief for everyone involved.

For my part, proud gate-goblin since 1999. Somebody gotta keep the riff-raff at bay, or we'll be up to our necks in idiots and activists 'afore the week is out.

LOL, ChromeOS is Linux... Just with more cloud/CaaS bullshit.

In my case they're just desktop files in /etc/xdg/autostart. Actually running them is up to an XDG compliant DE.
Anywhere else that has them start after session login should work just as well though.

Probably can't find any pidfiles, '--list' also needs the same '--pidfiles' argument you used when starting them, or a default set in /etc/daemon.conf

Yeah, elogind hooks need a version from unstable. >=0.8.2 IIRC.
See the "simple backport creation" debian wiki entry for an easy guide.