@bitprophet@mhoye I have the advantage that my bike club has historically started a lot of weeknight group rides (some of which I've led) from a place just down the street from this vantage point. So I looked at the original pano, even in potato form, and thought 'that looks familiar ... wait'.
@gvwilson The entire album is such an amazing thing that I've loved for years. (I should re-listen to it one of these days, somehow; my CD copy is still packed away.)
I like much of Copeland's work in general, but for this album in particular he hit out of the park right into my section of the stands.
@puppygirlhornypost@Binder And why bother monitoring the expiry time of private TLS certificates that expire in +10 years or more? Surely we'll remember then, if we even need them any more.
Really feeling my failing eyesight now that I'm having to choose between foggy glasses and no glasses. Wish some of the fancier masks I tried had actually fit me.
@bitprophet@basepi My Auras have been fog-free for me so far (even in demanding winter conditions that fogged everything else). I have to make sure the fit is right, but once it was I could even do things like bike (in the winter) in them. It was amazing.
Half formed hot take: the Linux kernel CVE situation is the tip of an emerging iceberg as OSS people push back and refuse to do supply chain/security work for free just because third parties want it.
(AFAIK, the ultimate trigger was third party maintainers of old kernels wanting the mainstream kernel to note all changes that turned out to be security fixes so the 3rd parties could backport them and only them. Identifying what is actually a security fix is non-trivial extra work (& fallible).)
Blog post: Some ideas on what Linux distributions can do about the new kernel situation https://utcc.utoronto.ca/~cks/space/blog/linux/DistributionKernelHandling2024
tl;dr: distributions can longer release whenever they want, have the same kernel version for years and years, and have great security (unless they want to do a lot of work themselves). But realistically they never could.
Volunteer run distributions should probably get used to updating their kernel versions over the lifetime of a release. Commercial ones? Whatever you'll pay for.
Blog post: The X Window System and the curse of NumLock https://utcc.utoronto.ca/~cks/space/blog/unix/XNumlockCurse
tl;dr: having NumLock on can more or less invisibly break key bindings because 'NumLock' is treated more or less like a modifier such as 'Shift'. And things can turn NumLock on for you, because they feel helpful. All of this is tangled up in how X turns keycodes into 'what they mean', or doesn't.
(Maybe X could do with another layer of translation; keycode → keycap label → actual meaning considering modifiers.)
TIL that Lustmord is on Bandcamp, https://lustmord.bandcamp.com/music
Now I have some catching up to do (and a Bandcamp Friday coming up, conveniently).
Shonen Knife is on Bandcamp, although not with their full discography (I assume some combination of rights issues and preparing digital releases). https://shonenknife.bandcamp.com/music
Shonen Knife makes great music that is not in the least bit ambient, and I have fond memories of seeing them live once.
Is there an idiomatic SQL (sqlite3) way of mapping a subset of selected records from a large table ("users") to unique values in a smaller table ("coupons")? It's easy enough to select all the user records not yet mapped, and to select all as-yet unmapped coupons, but then what's a nice clean way of mapping one to the other? Order doesn't matter, only that the mapping once established can be queried again in the future.
My brain is stuck thinking sequentially about this, frustratingly.
@Doomed_Daniel@vees@dan Server environments don't necessarily do MAC registration, and not all DHCP environments do authentication by MAC (but a machine may still want to keep a stable NIC name for eg its own firewall config).
Broadly: writing the new MAC somewhere is doable but it makes a stressful situation (hardware failure and replacement) worse. I once ran systems that needed this and it was a pain in the rear.
@Doomed_Daniel@vees@dan If you burn the MAC into the network device name, every system has a different name for its network interface, even on the same hardware, which is a sysadmin pain in the rear. If you freeze a simple network name based on the MAC and add a new network name if you see a new MAC, systems can wind up with network names depending on their history; reinstalling the system will give it different network names (because old MACs won't be claiming the good ones any more).
@Doomed_Daniel@vees@dan In many situations you don't want to keep the mapping file, because it creates differences between identical hardware based on the history of a particular server. One out of your eight hardware-identical fileservers having a different network name because you had to move it to the spare chassis (or swap its add-on network card) at one point is a special sort of hell.
(Also, not all reinstalls are planned in advance. Sometimes the disk blows up.)
@Doomed_Daniel@vees@dan I believe systemd creates aliases, or at least lets you set naming policies for devices, so if you want to use MAC-based names you can fairly easily. And the default PCIe based names are mostly stable, and sometimes systemd can actually detect that a network port is a motherboard port and give it a truly stable name.
(This depends on vendors getting various BIOS data right, which is rather variable.)