No, I figured if I could recall the name I could get a nostalgic fix by searching it. I found this:

https://en.wikipedia.org/wiki/DESQview

I recall DESQview was much lighter weight and better performing than Windows, but had limitations. I did not recall that the windows were text only within, but that’s starting to fill some holes in my memory.

To be fair, I was quite vague. I think there are multiple right answers… but I recalled one starting w/a ‘D’ and that’s what I was trying to recall.

In those days, DOS was the OS. Windows and DESQview were just window manager apps that ran other apps.

What is that? I don’t think that’s what I had in mind. I think it’s DESQview I was trying to think of. Anyway, not important… it was just driving me nuts I could not remember.

Originally ZFS could not be a boot disk because of the license issue. There was some other important feature that was denied to linux users, originally (forgot what it was). Apparently the booting restriction was eventually overcome. I don’t really grasp how the licensing changed that made booting possible.

Conceptually ZFS was relatively superior to all other filesystems. If it’s fully liberated, I don’t get why it is not more popular. I might expect it to be a default of sorts when installing Debian.

I have one as well, mothballed, which is why the article caught my attention. Then I saw all the mention of Cloudflare and thought: oh fuck, so it needs a wheelchair with a mouth joystick, in effect.

What originally attracted me was running a full-blown ZFS, which was too license encumbered to be fully featured in linux or bsd, IIRC. I never got around to doing much with it. And now I wonder if ZFS is finally fully liberated on a FOSS platform.

I have not tried much of anything yet. I just got a cheap laptop with a BD which came with Windows and VLC. I popped in a blu-ray disc from the library and it could not handle it… something about not having a aacs decoder or something like that. I didn’t spend any time on it yet but ultimately in principle I would install debian and try to liberate the drive to read BDs.

thanks!

Though I should mention my original motivation with makemkv was to rip blu-ray discs, which has complications that go beyond DVD. But the DVD guide will still be quite useful.

Well it’s still the same problem. I mean, it’s likely piracy to copy the public lib’s disc to begin with, even if just for a moment. From there, if I want to share it w/others I still need to be able to exit the library with the data before they close. So it’d still be a matter of transcoding as a distinctly separate step.

What’s the point of spending a day compressing something that I only need to watch once?

If I pop into the public library and start a ripping process using Handbrake, the library will close for the day before the job is complete for a single title. I could check-out the media, but there are trade-offs:

• no one else can access the disc while you have it out
• some libraries charge a fee for media check-outs
• privacy (I avoid netflix & the like to prevent making a record in a DB of everything I do; checking out a movie still gets into a DB)
• libraries tend to have limits on the number of media discs you can have out at a given moment
• checking out a dozen DVDs will take a dozen days to transcode, which becomes a race condition with the due date
• probably a notable cost in electricity, at least on my old hardware

Wow, thanks for the research and effort! I will be taking your approach for sure.

I’ll have a brief look but I doubt ffmpeg would know about DVD CSS encryption.

In principle the ideal archive would contain the JavaScript for forensic (and similar) use cases, as there is both a document (HTML) and an app (JS) involved. But then we would want the choice whether to run the app (or at least inspect it), while also having the option to offline faithfully restore the original rendering. You seem to imply that saving JS is an option. I wonder if you choose to save the JS, does it then save the stock skeleton of the HTML, or the result in that case?

wget has a --load-cookies file option. It wants the original Netscape cookie file format. Depending on your GUI browser you may have to convert it. I recall in one case I had to parse the session ID out of a cookie file then build the expected format around it. I don’t recall the circumstances.

Another problem: some anti-bot mechanisms crudely look at user-agent headers and block curl attempts on that basis alone.

(edit) when cookies are not an issue, wkhtmltopdf is a good way to get a PDF of a webpage. So you could have a script do a wget to get the HTML faithfully, and wkhtmltopdf to get a PDF, then pdfattach to put the HTML inside the PDF.

(edit2) It’s worth noting there is a project called curl-impersonate which makes curl look more like a GUI browser to get more equal treatment. I think they go as far as adding a javascript engine or something.

It’s perhaps the best way for someone that has a good handle on it. Docs say it “sets infinite recursion depth and keeps FTP directory listings. It is currently equivalent to -r -N -l inf --no-remove-listing.” So you would need to tune it so that it’s not grabbing objects that are irrelevent to the view, and probably exclude some file types like videos and audio. If you get a well-tuned command worked out, that would be quite useful. But I do see a couple shortcomings nonetheless:

• If you’re on a page that required you to login to and do some interactive things to get there, then I think passing the cookie from the gui browser to wget would be non-trivial.
• If you’re on a capped internet connection, you might want to save from the brower’s cache rather that refetch everything.

But those issues aside I like the fact that wget does not rely on a plugin.

The other thing is, what about JavaScript? JS changes the presentation.

Markdown is probably ideal when saving an article, like a news story. It might even be quite useful to get it into a Gemini-compatible language. But what if you are saving the receipt for a purchase? A tax auditor would suspect shenanigans. So the idea with archival is generally to closely (faithfully) preserve the doc.

IIUC you are referring to this extension, which is Firefox-only (likeunlike the save page WE, which has a Chromium version).

Indeed the beauty of ZIP is stability. But the contents are not. HTML changes so rapidly, I bet if I unzip an old MAFF file it would not have stood the test of time well. That’s why I like the PDF wrapper. Nonetheless, this WebScrapBook could stand in place of the MHTML from the save page WE extension. In fact, save page WE usually fails to save all objects for some reason. So WebScrapBook is probably more complete.

(edit) Apparently webscrapbook gives a choice between htz and maff. I like that it timestamps the content, which is a good idea for archived docs.

(edit2) Do you know what happens with JavaScript? I think JS can be quite disruptive to archival. If webscrapbook saves the JS, it’s saving an app, in effect, and that language changes. The JS also may depend on being able to access the web, which makes a shitshow of archival because obviously you must be online and all the same external URLs must still be reachable. OTOH, saving the JS is probably desirable if doing the hybrid PDF save because the PDF version would always contain the static result, not the JS. Yet the JS could still be useful to have a copy of.

(edit3) I installed webscrapbook but it had no effect. Right-clicking does not give any new functions.