The article does reflect the issue at the time (the media mafia's boogeyman "piracy") and the thought that to prevent piracy, users must be restricted from access to "general purpose computers".
> So personally I've found what i consider to be a safe alternative.
A bit more effort, but downloading the podcast and listening to it via a basic audio player app that does not further enshitify itself daily is even safer.
at some point ima stop being lazy and setup the reverse proxy for my jellyfin server and this will be a smooth "ytaudio {url}" alias that downloads through ytdlp and places it in the proper folder .
For now its a rare enough occurrence where i just keep neglecting it.
Tk's GUI object model is sitting at a reasonable maxima between trivial to make use of vs. triggering the events necessary to make the GUI active.
Small example. You want a button on your GUI that triggers a procedure called "process" when it is clicked, this is the code you need (if you are fine with the remaining defaults) (and assuming you used 'pack' as the geometry manager):
button .process -text "Process Entries" -command process
pack .process -side top
And a fully active GUI button will now appear at the bottom of your Tk window, with a label of "Process Entries" and when you click it, a Tcl procedure named "process" will be executed.
> when that page disappears after an acquisition or rebrand.
Sadly, it does not even have to be an acquisition or rebrand. For most companies, a simple "website redo", even if the brand remains unchanged, will change up all the URL's such that any prior recorded ones return "not found". Granted, if the identical attestation is simply at a new url, someone could potentially find that new url and update the "policy" -- but that's also an extra effort that the insurance company can avoid by requiring screen shots or PDF exports.
Good lord no, I would never work for that massively evil corporation.
I do, however, work for one that is deathly allergic to HTTP redirects and that changes the user visible URL's each time they change/move/update servers (or for practically any other change). So there's a constant churn of "project X is deploying to Y on date Z, the new URL will be Q" announcements -- and meanwhile, you find that any deep links to URL Q[t-1] also got changed up when date Z arrives and the URL becomes Q[t]. And then in a few months, the same game, only with URL Q[t+1].
If you are willing to sacrifice some storage space on the disk, then dvdisaster (https://en.wikipedia.org/wiki/Dvdisaster) can add extra ECC data to the disk that will allow recovery even if some percentage of the disk errors out upon read later.
Granted, if one no longer has the mechanical drive, or if the disk errors out beyond the threshold where the extra ECC can correct the errors, the data's still lost. But it (dvdisaster) does provide some protection from the "bit-rot" case where the disk slowly degrades.
Way back (circa 1988ish timeframe) I remember a digital logic professor giving a little aside on the 8087 and remarking at the time that it (the 8087) used some three value logic circuits (or maybe four value logic). That instead of it being all binary, some parts used base 3 (or 4) to squeeze more onto the chip.
From your microscopic investigations, have you seen any evidence that any part of the chip uses anything other than base 2 logic?
The ROM in the 8087 was very unusual: It used four transistor sizes so it could store two bits per transistor, so the storage was four-level. Analog comparators converted the output from the ROM back to binary. This was necessary to fit the ROM onto the die. The logic gates on the chip were all binary.
https://opentaxsolver.sourceforge.net/
reply