Not ashamed to admit
that my first thought when reading this news was about Asahi Linux. In my defense, this beer is not easy to come by in my corner of the world.
89 publicly visible posts • joined 2 Feb 2022
Google is in a lose-lose situation:
- Most users will mark as spam annoying e-mails instead of unsubscribing (usefulness/wisdom in clicking the unsubscribe button notwithstanding[a]) or writing a filter to discard the e-mail.
- Do-Not-Call[b] equivalent registries/laws in many (most?) countries have exceptions for political messaging, and IIRC the US is very much one of them.
[a]: For blatant spam the cybersecurity recommendation is to not click the link, as it signals to the spammer that the e-mail address is valid and being read. In my experience however, it worked wonders.
[b]: I know the issue is with e-mails, but it's kind of the same principle.
There is still some business/good synergies[a] you can do in those conditions. Before being acquired by Intel, Altera contracted (nearly?) exclusively with Intel's foundries in a bit of a win-win: Altera got a little discount, Intel got the perfect guinea pig for new processes (FPGAs apparently are relatively simple/fault tolerant ASIC designs).
[a]: Sorry for the marketdroid lingo; if it makes any reader feel better, I threw up as I was writing it.
For one-off/"data recovery", you use the recovery code (which you did store in a secure, retrievable place, right? :O ); for transferring the disk to a new motherboard/machine I would expect a command to (re)enroll a TPM key[a], but I wouldn't expect it to be available yet.
Note that "the key" isn't what's in the TPM/what you type in the password/recovery box. "The key"(s) is(are) stored encrypted on disk, hashed/encrypted/protected by the TPM/recovery code/password. LUKS allows you to have multiple passwords that will work equally as well for each volume (8 or up to 32 depending on whether it's LUKS1 or LUKS2), and in my notebooks I use that to enter my passphrase once on boot. I only have the EFI boot partition unencrypted; GRUB stage 1 asks for my passphrase to decrypt its stage 2, and then I have a different key on the machine's initramfs which avoids Linux from asking the passphrase again.
[a]: Dunno how it works on Windows/Bitlocker, but on a machine I was setting up with dual boot I had issues with the TPM refusing to provide the decryption key; I fully expect that after entering the recovery code Windows threw away the TPM key and generated a new one.
Until about two-three years ago, I used one of the AUR versions of Firefox (firefox-kde-opensuse) as Firefox had zilch integration with KDE and I intensely dislike the GTK ≥ 2 "save dialog" enough to build Firefox from source. Nowadays, Firefox integrates with xdg-desktop-portal which solves that issue; it's not full integration (among others, Firefox doesn't use KDE's MIME default programs nor the print dialog), but it's enough for me (and in my experience GTK/GNOME's print dialog works better with discovered network shared printers[a]).
The other browser-adjacent app I have is Ferdium (a twist on the multi-account chat client), but I use the build-it-from-source package to use the system-wide electron installation I already have 0:)
[a]: KDE's print dialog sometimes will gray out the double-sided print options even for printers that support it.
If you frequent meme pages/boards and/or "gif hosts", most "gifs" nowadays are actually .webp or straight up MPEG-4 video ("DivX")/x.264 with no audio track. Said pages will still serve .gif files if coaxed, but will prefer nearly anything else first.
APNG has pretty much been killed dead by Chromium refusing to implement the standard. I doubt there will be a resurgence, but I hope I'm wrong as back in the day it was much smoother than .gif.
My favourite is Windows.old. Supposedly created when upgrading between editions (ej, 23H2 to 24H2, 10 to whatever 11 version), some official Windows ISOs (24H2 at least) come with that folder already created, which means that image customization via sysprep fails when installing (for whatever reason, the installer throws a fit when trying to create that folder from the installation image). Also an honourable mention to "System Volume Information" which looks like it has some critical filesystem info, but it's "just" for System Recovery.
Google Drive has this exact same "feature" (putting shortcuts to the webview of shared folders instead of the actual sync-ed folder) by default. There is an arcane, not officially documented workaround and a promise to properly support this use-case, but it's been broken since at least the before times (~2019, likely earlier). Dropbox works exactly as the user would expect, and I assume so do OwnCloud/NextCloud.
YMMV and all that, I've had had an equivalent experience: the high to mid tension transformers in my area[a] caught on fire during routine maintenance and there was a ~9 hours outage in my neighbourhood (plus ~9 months under emergency power with lots of 20ft/40ft containerized diesel generators provided by the utility company until the new transformers were commissioned). My ISP (Cable company) outlasted my cellphone service[b] (I only lost service the next day due to reboots in their last mile equipment).
If you go that route, buy a Jackery or similar outdoorsy unit[c], as they all come with Lithium-Ion or similar batteries with much better capacity/density. Your normal run of the mill Lead-Acid UPS (at least one rated for ~1000VA with passive cooling) will last about 30 minutes to an hour[d] with that load without extra batteries.
[a]: ~1sq kilometer
[b]: Had my telco modem and my router with an UPS, would turn it on occasionally to check as I was curious :)
[c]: I hate the fact that these don't come with the monitoring hardware an UPS would have/NUT compatibility, as I'd change my current home UPS(es) for these in a heartbeat
[d]: YMMV, runtime is depends on battery capacity, UPS efficiency, and load characteristics and follows a negative exponential curve, many people with long runtime/low power requirements tend to oversize the power load rating of the UPS as that does tend to get you bigger capacity but you should bite the bullet and buy the battery expansions if available for your unit
This happened at my work (University adjacent). About 12 years ago at work, dunno what was the issue the punter had but I solved it by setting up a shared connection in Ubuntu (with NetworkManager), and having them connect to the internet via Wi-Fi. ~1 month later, I had an intermittent issue with a rogue DHCP server on the network that I couldn't make heads or tails of. One day in anger I traced the suspect switchport[a] and disabled it via software. Within a week I had the main suspect on my office complaining about not being able to use the port; I enabled it and went to their desk to find the shared connection was coming up by default. After admonishing them (while taking my fair share of the fault), I disabled autoconnect on the shared connection and showed them how to check if they were using the correct connection. Within the year I configured every switch I could get my grubby hands on the admin console with the allowlist of ports that may send DHCPREPLY packets.
[a]: Luckily it was on one of the switches I could admin back then,but that's a different story.
... but their hardware (paired with OpenWRT) is very good for the price, and they have been trying on the security front; in particular, their OOB prompts on newish devices (AX23/WiFi 6) seemed to be a pretty good UX and really insisted on you changing the password. Secret services shenanigans notwithstanding, can't really say TP-Link is significantly worse than other consumer-grade brands.
That said, they seem to be complaining mostly about ISP-supplied equipment, which is typically not user-upgradeable (and in many cases, not even user-configurable). In my corner of the world, On-Premises equipment is only replaced on failure, on speed upgrade not supported by your current device, or when you change ISPs.
Nvidia had at least two Pentium 4/Bulldozer moments, in the mid 2000s and late to mid 2010's. In both cases, they were helped by the fact that ATI/AMD drivers were awful, and in the latter case by CUDA. Nowadays, their grip on the datacentre industry with CUDA would help them weather the fallout for a good long while.
So it did! From my reading of the fine documentation[1], PCI(e) Passthrough, USB passthrough for USB >=2, and disk emulation beyond IDE, SATA (which used to be locked way back then), and virtio is now part of the base FOSS package. For my particular VM use-case PXE is a rather firm requirement[2], but I will agree the FOSS Virtualbox covers what most(/ly) reasonable people would need/expect of a desktop virtualization solution.
Thanks for the heads-up!
[1]: Which contradicts Oracle's own Virtualbox microsite :)
[2]: Could mostly work-around that, but it'd involve copying ISOs around. (I use Full-fat VMs -- KVM/QEMU via libvirt with virt-manager as a front-end -- mainly for testing my PXE servers, at home and at work :))
First thing that came to mind was VMWare under the Broadcom umbrella, although to be fair Oracle's VirtualBox has had a massive red pill[1] for far, far longer than Oracle Java's[2] (and Oracle Java's red pill is COVID-adjacent).
[1]: The proprietary VirtualBox extensions (needed/beneficial for all but the most basic VM usage scenarios) under their bespoke PUEL (Personal User Evaluation License), free only for non-commercial use.
[2]: Oracle Java Red Pill (if it's the first time you've heard of this and rely on Java, go forth and install OpenJDK's JRE/JDK ASAP).
Never really used VMWare, the biggest ticket feature when compared to VirtualBox is mature 3D virtualization[1] support on both Windows and GNU/Linux guests (AFAIK, VirtualBox only supports 3D Virtualization on Windows guests, QEMU/KVM only supports 3D virtualization on GNU/Linux guests and may not be quite stable yet).
[1]: As in "translate 3D commands from the guest into the single GPU on the host", not "give this entire GPU to the guest OS"
ASIC design house is not an asset to sniff at, even if fabless. Besides, FTDI chips are still the standard/default[1] choice in USB to serial/SPI/I2C/GPIO/weird in-house programmable protocol[2] you may need, and they're a valuable debug/development tool in electronics (to the point most SBCs -- a la Raspberry Pi -- include an USB to Serial chip straight on the PCB for console/log access).
In my experience, USB to serial FTDI chips (as long as they're the genuine article) had the best Windows compatibility by far (other than the Arduino thingamajigs that use alternative chips); dongles with other chips (esp. those with Prolific) depended on how many corners the dongle-maker cut (on Linux -- GNU or not -- I've never had any issues with any chip as long as the driver was available).
[1]: Despite doing some very dodgy stuff with their windows drivers (search elReg for more, and note that the fallout of these changes was felt mostly on customers who bought a product that used the counterfeit chip -- whether on purpose or because the OEM was scammed by their suppliers)
[2]: FTDI provides a closed-source SDK to wrangle control of their more feature-full chips which allows uses like implementing an USB to JTAG dongle.
It's somewhat sadder IMO. The project has a 1-command upgrade: install the new version side-by-side, run pg_upgradecluster {old version} {cluster} for each cluster in the local installation[1], bob's your uncle). However (at least on Debian/Ubuntu[2]), it won't be handled by the package manager if you used the default, ready-to-use cluster ("main") because it is automatically created on the new version and pg_upgradecluster refuses to overwrite a cluster on the newer version.
[1]: If using multiple clusters (groups of databases), you can upgrade at your leisure as long as you don't uninstall the old postgresql version
[2]: I run non-critical DBs (some downtime allowed) both using packaged from the official postgresql debian repo (at work for gitlab and other web apps that use postgresql as their backend, typically using the latest version) and the version from debian stable du jour (at home, for tt-rss). Always had that problem.
...this will be used to either extortobtain some steep discounts from western providers ("nice sales you have here; would be a shame if your product were to be ZTEd into oblivion"), or to justify a pivot into 100% organic, home-grown, BPA free silicon (with popular support to understand/eat the pain/fallout of said transition). As someone in South America, can't really blame China for foraying into either of these options.
....oh....I wonder how much Cisco kit there is in China.....
My gut feeling is very little (given how hard 5 eyes hammered Huawei/ZTE/Zyxel in the telco equipment space), but I can't discuss "private" companies buying cheap-as-chips used/refurbished western networking equipment.
At that time, the Reg FOSS desk was reveling in the raw speed of a 512 kbps ADSL connection through an Alcatel Speed Touch modem.
My first Broadband (for the time) connection was a blazing 256kbps downlink with a successor to that line of modems (Alcatel SpeedTouch 330) in ~2003-2004; the telco in my neighbourhood had a relatively cheap as chips plan where you could browse at night (from 20:00 onwards) and throughout the weekend, or pay a surcharge when browsing outside that time. One of the first things I did was search how to make it work on GNU/Linux, which I managed to do and felt like an absolute hacker (IIRC, the only tricky/fiddly parts were getting GNU/Linux to load the device firmware, and getting the ISP ATM parameters; luckily my ISP had pretty standard parameters so that bit was a cinch).
IIRC, apt-rpm was originally developed by Conectiva Linux (Brazilian distro which was eventually bought by Red Hat and became their Brazilian offices).
Mandrake was the first GNU/Linux distro I installed in "my" (family) PC[1], and to this day I have extremely fond memories of it. It did come with one of the first apt-get equivalents for the RPM world (urpmi, still used by Mageia AFAIK), although by the time I was getting proper proficient at CLI I was jumping into (K)ubuntu. I still miss the Big List of Software in the installer, as the last step before installation...
[1]: As a dual boot with Windows XP in ~2002-2003; I gradually started using GNU/Linux more and more, until by Windows 7 I was only booting Windows for some games, and by the time Windows 8 rolled around I was 100% GNU/Linux on my home.
...as (officially) you need to step through 22.04 (Jammy Jellyfish) first :).
Joking aside, despite the extremely convoluted and messy development cycle (64-bit time_t migration on Debian's side running late, XZ kerfuffle, some last minute issues in LTS-to-LTS upgrades pushing that milestone back a month, some iffyness on the first stable Ubuntu 24.04 ISO when netbooting), the upgrading experience has been mostly smooth (had only one server where the upgrade misbehaved, and even then it wasn't too bad to finish the upgrade before rebooting).
That said, in my experience with *buntu, the only truly hairy upgrade was from 14.04 to 16.04 (AKA the systemd one), as you really needed to reboot/power-cycle your device the moment it finished or you were looking towards a dirty shutdown. Although I will admit the upgrade process on both Ubuntu and Debian leave a trail of unsupported packages that need manual intervention to remove which, on Ubuntu at least, should be handled better.
However the version supplied with Debian is dynamically linked (...)
Debian does provide a busybox-static package which does exactly what it says on the tin. Although by the time a system is that far gone, I personally go straight to PXE, my Ventoy pendrive (complete with SystemRescueCD and the latest WhateverBuntu LTS), and/or (for RPis and similar), an SD reader + systemd-nspawn + qemu-user-static-whateverArchitectureTheImageUses.
I meant it as "too fast" (as in somewhat soon-ish, I still have nearly two months left). I will admit I mostly heard the phrase from the FSX era of AirForceProud95 :), usually in videos where he was playing ATC, meaning either "airplane is coming too fast" or that the pilot seemed to be operating in "I'm landing now, good luck everybody else!" mode.
Haven't really checked it out fully, but archive.org has a not-so easily findable dump of UserFriendly strips that appears to be complete (alternatively, WaybackMachine seems to have the entire site crawled).
Also, I'm 36 (coming in hot on 37) and very much old enough to have (correctly!) noob-level fiddled with autoexec.bat on DOS (and possibly config.sys, but I don't remember that). It was on a Pentium 3 PC with Windows ME[1], "famously" incompatible with DOS programs (about as incompatible as XP). There was a way/"hack" to mostly re-enable DOS, which I had done to try and play some DOS games that wouldn't run on ME, and I would fiddle with autoexec.bat (possibly config.sys) to load/unload TSRs at boot time/fiddle with the amount of free low mem.
[1]: It's probably the least hardware-compatible Windows version ever, and among the worst for software compatibility, but
a) With supported hardware it worked just as badly as 98/98SE
b) User Experience wise, it was still better than Vista/8[2]
and I will die on both hills.
[2]: An absolute shame, as both Vista and 8 brought actual, good internal improvements that "we all" misattribute to Windows 7/10.
ssh -X, ssh -Y, and Xpra work just as well on Wayland as they do on X11, thanks to the magic of XWayland currently being a required component of both GNOME's and KDE's Wayland sessions. Not to mention that there are Wayland versions of RDP/VNC clients. TeamViewer also has support for remoting into a Wayland session, and both KDE and Gnome have/are about to release off-by-default support for RDP-ing into a running Wayland KDE/Gnome session.
You're cheating, your solutions all use X or full desktop sharing!
You never specified I couldn't, the requirement was "run GUI apps remotely on a local Wayland session", and you very much can! 0:)
But they're gonna take that compatibility away because they're all against me and good ol' technologies! What then?
Can't comment on the second half, but yes, X11 compatibility is more likely than not going away in an unspecified time frame (there are -- pre-release? -- versions of at least one of GNOME/Mutter or GTK that can be built without X11/XWayland support). If/when that happens, there is waypipe. It's not the be-all end-all user experience (uncanny-valley invocation compared to ssh -X, noticeable more jank than Xpra -- still largely[1] within the same ballpark) and it requires installing it on the remote end (like Xpra), but it has similar performance to Xpra (both waypipe and Xpra are much kinder than ssh -X on bandwidth, almost on par with RDP/TeamViewer/etc).
PD: I get legitimate gripes with the current state of Wayland/Wayland app support (accessibility and Chromium-adjacent software not enabling their existing Wayland support by default being the more salient ones), I get "as it is I can't use this", I even "get" not liking change, but at least come at Wayland with actual, legitimate gripes. What I don't get (or at least, find extremely self-conceited) is "I refuse to adapt to anything new", and "I will stay with (blah), and the whole world shall keep maintaining it in production-ready until I get bored with it", for any value of (blah). Personally, the two big blockers I encounter in my own tech bubble are:
- Flickering XWayland windows on KDE when using Nvidia graphics cards (solved in Plasma 6.1 + Nvidia driver 555 series and up, but those are not yet available on Ubuntu)
- No support in AnyDesk for remoting into a Wayland session
The first one doesn't affect me (I don't own/regularly use a PC with Nvidia graphics), the second one only affects me in the PC my parents use, and even then I haven't had to AnyDesk into it in years now.
[1]: Unlike Xpra, it exposes you to this issue if running GTK4/Gnome applications from a KDE local endpoint (with the workaround being to install icon packs on the remote end).
FTF(ine)A:
Imposing a requirement to verify a laptop's serial number during onboarding is one way employers can catch a laptop farm user pretty quickly – those with physical access would be able to find that in a pinch.
This is rather trivial to do for the vast majority of notebooks (both on Windows and GNU/Linux) if the user has a modicum of IT competency. Asset number would be a better candidate depending on company policy (many BIOSes -- esp on Laptops and large OEMs -- have a write-once field for asset tag management; if the tag is set there it is just as easily readable).
None of these features, in any of these apps, can survive a photo/video camera/screen recorder[1], and for the most part are advertised as such. However, "not even attempting to hide the message from a client we know for a fact can't/won't do the right thing" is very low-hanging fruit, esp. for a platform where all clients are developed in-house[2].
[1]: Cellphone apps will put up a fight against screen recorders when running on hardware/the same VM tho.
[2]: The only "third party apps" I know for Whatsapp straight-up load the web version (Ferdi/Ferdium/etc).
Was a teenager at the time and my first PC with >= 4GB was running 64bit OSes already, but IIRC Windows XP Pro 32-bit has off-by-default PAE support (magic intel instructions available on every -- most? -- i686-and-up CPUs to address up to 64GB of RAM iff the OS/software has been coded for it[1]). Wouldn't have helped/made sense for 4GB of RAM as it incurs a performance penalty, but it was there.
[1]: The quick n' dirty explanation is that it sort-of works like segmentation: you get an additional 4-bit memory addressing register; apps/OS can then address up to 64 GB of RAM in 4GB chunks. Programs not coded for PAE will run, but can only address/access 4GB of RAM.
There are quite a few self-hosted TeamViewer "clones" (one such alternative, not yet used by me), although depending on your needs, you may need a beefy server/network connection (you're live-encoding video).
I will admit that the three times I bought an Nvidia GPU (2007, 2012-ish, 2016-ish) quality of drivers (esp. on GNU/Linux) was my main concern. However, right now the big advantage Nvidia has for all non-home/non-mobile workloads is CUDA (not necessarily because it's better than OpenCL et al, but due to being first and therefore having lots more compatible software). On the home PC market, Nvidia (and AMD) have the advantage of having humongous piles of workarounds for specific games (which Intel should've also had from their iGPUs...), and AMD currently also have decent drivers. Still, Intel launching a GPU with essentially no driver support for DirectX < 12[1] was one of the decisions of all time. Props to Nvidia for having the best money-no-object hardware of the current generation (RTX 40X0), and likely the next one too.
IFF Samsung is throwing their hat on designing/building their own GPUs for the mobile market, driver support should be easier than on PC. The mobile GPU market is already much more heterogeneous than PC GPUs, and the chances of Google/Phone Manufacturers doing patch releases of their GFX stack to support badly coded games is much lower.
PD: From hearsay (and some personal experience, esp. near 2007), ATI/AMD drivers varied between almost tolerable (mostly on Windows, usually near or after the cards went EOL) to unmitigated disasters (esp. on GNU/Linux). It only got better around late 2010s, to where all my daily PCs sport integrated or external AMD GPUs and I couldn't be happier about them. (The only remaining issue I personally had -- also with Nvidia but not with Intel iGPUs -- was hangs after kexec, but it seems to be finally fixed).
[1]: Intel straight up use vkd3d/dxvk (as seen in Wine and Proton) for DirectX 9/10/11 support.
... Unity was (is?) dope, especially against Gnome 3.x/4x. The bit I liked/respected the most about it was how easy it was (well, would be/have been if I had sat down and tried to learn how) to navigate the entire desktop with keyboard shortcuts. Especially the discoverability of the keyboard shortcuts (I always got the sense the environment tried to push you into using them). And as much as we riff on convergent interfaces in this echo chamber, Unity was the second least offensive for PC users ( with the inverse podium led by KDE :) )
Modern gnome at least has text search when pressing the Meta (Windows) key; vanilla-ish (as seen in SystemRescueCD and Armbian) XFCE doesn't even show its menu when pressed. Not a big deal for me personally as I use Alt-F2 for the run command[1] and then mostly go straight for a terminal and/or Firefox, but still.
[1]: Which is embarrassingly better than Gnome 3's not-even-a-browse-button version (haven't checked on Gnome 4x yet).
Gonna have to play a bit of devil's advocate here :)
Gmail is something similar to email, but different. Its "labels" system is non standard and IMAP clients do "more or less" work.
That it is, and as someone who is a born-again desktop e-mail client believeruser, it really messes them up and I have some resentment that google never seemingly bothered to make a specification for tags. They do add actual, useable, sensible features over IMAP folders tho (just because I don't use those features doesn't make them meaningless)
Also, their antispam rules are obscure and if you are "bad" in their eyes, like my domain is, there is NO WAY you can actually ask them what's wrong. You are just fucked.(snip to your other reply)Microsoft is not so bad, it has a procedure for requesting delisting that works.
My experience was the exact opposite as yours. I've had spam issues with my e-mail server twice (compromised accounts), and once I stopped the flood of e-mails (and requested delisting from the e-mail provider neutral denylists) I had normal service against every e-mail vendor within 6-24 hours ... except Microsoft (which is the provider of choice for an institution we have close ties to), which took a good week to stop black-holing our e-mails (which gmail didn't do), and either I couldn't find the form/procedure or Microsoft did nothing with it (last time was a good 6-7 years ago at least 0:)).
I will say, I still resent google for demanding either proper valid SSL/TLS certificates or no encryption when using the "check other e-mail accounts"[1] feature back in December 2011/2012, without any warning, a full 5 years before LetsEncrypt >:(, while I was on vacation, and with most of my workplace syncing their accounts with gmail.
[1]: To this day they don't demand proper certs for SMTP, only for POP3
The vendor is mostly google itself; they design the server hardware and pawn it off to an OEM for manufacturing. Server software is their own in-house (GNU?/)Linux distro with their own software. I wouldn't be surprised either way if their SAN/Storage and networking was COTS or their own design.
Facebook/Meta does something similar, and has even made a standard out of it.
For all the flak Raspberry Pi has gotten thanks to its relative hardware value and scalping/shortages during the pandemic, I always felt the value was always on the documentation and software support: actual documentation, properly updated, mostly compatible with the parent distro Official OS image, open source hardware/IO access libraries. Bit of a shame about the GPU situation but overall understandable/forgivable. They are by no means perfect (nothing is), and I understand the criticisms about focusing on embedded/industrial clients to the detriment of the thinker community and even the armbian project being pretty salty about no "upstream" Pi support, even if I find them largely overblown.
(Note: Never bought one nor similar products -- my interests starts and mostly ends on spinning-rust NAS oriented boards :) -- but used/fiddled with most full-fat Pi variants at work).
My quick and dirty duckduckgo-ing netted me some references in example unbound configs, but not what the domain is. Didn't search the unbound repos (don't feel like logging into github, couldn't find the template config file in a quick peruse of the files), but an answer may be there
That's a tricky question! On the one hand, it shouldn't be able to as all streaming services deliver DRMed content through WideVine[1], and by the time you're doing that. On the other hand, Spotify does the same and Spotify ad-blockers are very much a thing (although not as a straight request block a-la UBlock Origin, they seem to work by injecting JavaScript that skips the function/callback that plays ads and tricking the webapp into thinking that everything is A-OK).
[1]: DRM standard for the web; Firefox has the option to disable this content, as it works by running an obviously closed-source sort-of plugin. Youtube (non-paid content at least) doesn't bother with this, which is why it remains relatively easy to block ads/straight up download videos.
... no GNU/Linux distribution officially recommends such an upgrade path. The closest I've quickly googled is Debian (ElReg article describing such an adventure). Microsoft letting OEMs continue to sell x86 Windows past 7 on new machines (as opposed to getting the user to download and reinstall if they absolutely had to for whatever reason), on the other hand, was proper bad.
(Yes, you can significantly ease the pain of a reinstall in *NIX -- except macOS for the most part -- compared to Windows by doing a backup of /etc, /home, and most of /var; personally, by the time I've resigned myself to a reinstall I prefer to start minty fresh -- no pun/distro ad intended :) ).
And while this writer is not much of a gamer, we are told that a lot of games are still 32-bit and won't be updated. That was the main reason that Canonical backed down on dropping 32-bit support back in 2019.
Ostensibly the main driver (complaint) back then for keeping 32bit support was Wine, which needed 32-bit host libraries to run 32-bit programs (likely the vast majority of programs one would try and run under wine). Since then, Wine library loading has been completely reworked and you should "now" be able to use a single wine executable linked to your system's fully native 64-bit libraries and run 32-bit Windows binaries. However, 'tis true that Steam native Linux games are built against an Ubuntu LTS release which may or may not be 32-bit
Now, the last current browser for these old macOS releases is Firefox 115 ESR.
Which should be supported until a bit after Q1 2025
(On a personal note, I never thought I'd get to see the 32bit x86 mass extinction event this early. Mac is going through its 3rd to 5th such event -- 68k->PPC->x86(->amd64)->Arm, OS Classic -> OSX during the PPC days -- but it's a first for most x86 Windows/*Nix[1] users)
[1]: The only similar event(s) I can recall were on GNU/Linux before I had even heard of it: the switch from libc5 back to glibc, and on a smaller extent (with the same borkage capability), the switch from a.out to ELF.