Shitty drivers blaming the equipment as usual instead of how terrible their right foot is.

Qubes OS

3 words: Gravis PC Gamepad

Always keep an empty chip bag with you.

The phrasing and pacing sound repeatedly “but wait there’s more” style that AI seems to favor. Always trying to re-emphasize a point already made to make the reader interpret it a specific way.

Not to mention the em-dashes.

Sometimes good writing sounds like that too, but good writers also know to not use and repeat that same style over every paragraph.

Fascinating data presented in a clearly AI written or at least heavily edited format that makes it really hard to read without massive skepticism.

Good list. Two things I’d suggest: plastic bags and paper towels. Lastly, instead of the supercapacitor jumper, look for ones that use LiFe batteries instead. Those can be safely stored at full charge.

Wouldn’t be the restaurant harvesting. They likely only got the app out of convenience and sold to them as a cost savings; the actual ordering/menu company probably has all the customer data sharing agreements that the restaurant owner didn’t read or didn’t care enough to understand. Those companies are the ones who want your data, the restaurant doesn’t care.

Depends on what threat you’re protecting against IMHO.

If you’re trying to be anonymous, connecting to your home IP first is a dead giveaway to who you are. Both your home ISP and whichever ISP you’re connnected to will know.

Only easy way to maintain some anonymity right now would be to use Tailscale’s Mullvad integration……Tailscale to connect your servers, Mullvad for anonymize/country changing.

Other way might be to ONLY use Tailscale/Mullvad, and set up an alternative auth front door to your own network. Complicated and doesn’t work as nicely tho.

You’re 12 right?

It’s mainly of “you need to go a lot faster than an airplane does”, which means the engines needed to go that fast need different fuel, and when you go high enough you don’t have enough air to burn the fuel with so you have to bring your own, which means your spaceship now gets bigger and heavier……which means bigger engines and more fuel and oxidizer.

And then the lift part……air provides the lift, but there’s less air the higher you go, until you hit the point where you both don’t have enough air to hold you up AND you don’t have enough air to feed your engines.

So with that combination, with current technology, it’s only feasible to go up as fast as you can to get out of the atmosphere, then go sideways as fast as possible to get to orbital speed. Hence the current launch paths.

Director of acting intelligent

Heh true enough. And you can run into issues with package updates breaking something. But hopefully that breaks things for others too so there’s some shared misery there rather than just having to curse your past self for decisions you no longer remember? 🤣

DHCP can be set to specifically assign the same IP to specific devices, reserving them and ensuring that no other systems will use the same IP accidentally. So your servers will consistently get that same IP address assigned to them every time, no worry about the ip address changing unexpectedly.

Very old school; yes you can certainly do all of that and track all of that yourself. We all used to do it that way……But it’s 2026….just as you’d use a real editor rather than edlin, or password managers rather than text files, the new ways ARE better, easier and more consistent. Making sure dhcp works is one of the modern (honestly not that modern) basics that make sure your network is set up properly and isn’t hiding some misconfiguration gremlins that only work because of some static ip and route workaround you implemented years ago and worked “until now”.

Wrong. It’s 2026. You should be setting static dhcp entries and using dhcp to ensure static IPs, not avoiding dhcp. Using manually assigned static IPs just means you’ve built a fragile unique snowflake.

Yeah but they probably run windows and have shit tons of preinstalled crap. Unless Linux is well supported on those, that just tanks value.

Silly customer! You cannot hurt a Twinkie!

He taught me Roy G Biv

Code sloppering

How small are these devices? I think the other problem is that neither BTRFS nor zfs really are suitable for removable devices, and definitely not for ones smaller than probably 8Gb at the very least.

Unlike NTFS which is just a file system, both BTRFS and ZFS do volume management too, so it’s not just a single partition thing; they prefer to take over an entire volume and manage everything.

So while they’re the closest filesystem with NTFS-like transparent compression……they don’t match exactly.

I also hazard to guess if the devices you’re using are too small to accept a BTRFS formatted volume, no amount of compression is going to be enough to fit what you need.

If you just want to play with a bunch of small old devices……maybe play with LVM and small RAID arrays and configurations instead. You can the build a bigger volume out of a bunch of those disks together and then put a BTRFS or zfs volume on them. Can be fun to experiment and learn with anyway.