That mnemonic is misleading if it’s not gzipped, and unless you’re untarring a stream from a pipe or over a network, you don’t need to tell tar what compression was used when extracting, it knows.

So the onus is on every individual user, to pick a random ULA prefix, bind specific addresses from it to the loopback interface, which is a different procedure for different OSes, probably requires root or elevated privileges, can have hard limits on, document it, etc. Greeeeaaaaaaat design. IPv6 gives out /64 like they’re about to turn bad, but can’t spare a /104? Gimme a break.

I can dig a hole with a spoon, too, but if someone made it so that no one was allowed to dig holes with shovels unless they build their own (and have permission to build the shovel), when previously everyone was allowed to dig with shovels, I would not think highly of that person’s wisdom.

Maybe you think G. Huston of APNIC and W. Kumari of Google don’t really know what they’re talking about?

IPv6: Fuck you, you’re only allowed one, now. Yeah, yeah, I know there are about 340 undecillion addresses in the space, but I know better than you, no one in history has ever needed to bind different services to the same port on the loopback interface, and if they did they were doing it wrong. Oh you made an RFC draft? Well I let the one from 2015 2012 expire, so good luck with your current proposal, pleb.

Controls have to be put somewhere, and networked interfaces mean fewer physical controls that may be difficult to access, tampered with or fail. Having a standard control protocol means interfaces can be changed and improved without modifying the hardware. They’re not a bad thing.

However, having networked controls exposed on anything other than private, air-gapped, wired-only LANs seems rather foolish, to me.

And you can use its image creation tool to write a Windows installer .iso to a thumbdrive, for others who absolutely have to have it!

Fucked if I can work out why downloading the Windows .iso in Linux and writing it to USB has not once resulted in a bootable medium for me, despite literally every non-MS .iso working perfectly with the same tools.

Using a widely-available phone with good performance, decent quality, and long term security support, meant that more people could access it. I still can’t buy a Fairphone without going through an overseas middleman, then hoping I have no warranty issues, because they don’t sell to Australia. If something goes wrong with my Pixel, the shop I bought it from is minutes away.

I made the mistake of creating a Windows VM and believing their minimum required disk space figure of 64GB. It won’t upgrade. Asks to attach an external USB drive because it lacks enough space. It hasn’t anything added to it, only some bloatware removed. Attempting to upgrade takes hours, fails (despite attaching the extra storage), then restarts the entire download and install process over again. I can only assume it’s incapable of caching and verifying downloaded content. There’s no offline installer option, like we used to have with service packs. The whole thing is slow as molasses yet it doesn’t max out the 8(!) CPUs allocated to it. The host has plenty of spare capacity. It’s a steaming pile of shit.

Linux guests run fine.