3 ms·

Have you https://addons.mozilla.org/firefox/addon/single-file/ https://addons.mozilla.org/firefox/addon/single-file/? If you really just want the text content

by mikae1 8mo ago

Have you https://addons.mozilla.org/firefox/addon/single-file/ https://addons.mozilla.org/firefox/addon/single-file/? If you really just want the text content you could just save markdown using something like https://addons.mozilla.org/firefox/addon/llmfeeder/ https://addons.mozilla.org/firefox/addon/llmfeeder/.

ninalanyon 8mo ago
On the subject of SingleFile there is also WebScrapBook: https://github.com/danny0838/webscrapbook https://github.com/danny0838/webscrapbook I prefer it because it can save without packing the assets into one HTML file. Then it's easy to delete or hardlink common assets.
- venusenvy47 8mo ago
  I see that it gives three choices for saving the assets: single file, zip or folder. Is the zip version just zipping the folder?
  - ninalanyon 8mo ago
    I don't know, I've never tried it. I picked it because of the folder option which makes grepping for content easier and faster.
O1111OOO 8mo ago
> Have you https://addons.mozilla.org/firefox/addon/single-file/ https://addons.mozilla.org/firefox/addon/single-file/ Yes I have. I tried maff, mht, SingleFile and some others over the years. MAFF was actually my goto for many years because it was just a zip container. It felt future-proof for a long time until it wasn't (I needed to manually extract contents to view once the supporting extension was gone). I seem to recall that MHT caused me a little more of a conversion problem. It was my concern for future-proofing that eventually led me back to "Save As..". My first choice is "Save as..." these days because I just want easy long-term access to the content. The content is always the key and picking and choosing which asset to get rid of is fairly easy with this. Sometimes it's just all the JS/trackers/ads, etc.. If "Save as..." fails, I'll try 'Reader Mode' and attempt "Save as.." again (this works pretty well on many sites). As a last resort I'll use SingleFile (which I like too - I tested it on even DOS browsers from the previous century and it passed my testing). A locally saved SingleFile can be loaded into FF and I can always perform a "Save As..." on it if I wanted to for some reason (eg; smaller file, js-trackers, cleaner HTML, etc).

by mikae1 8mo ago

ninalanyon 8mo ago

On the subject of SingleFile there is also WebScrapBook: https://github.com/danny0838/webscrapbook https://github.com/danny0838/webscrapbook I prefer it because it can save without packing the assets into one HTML file. Then it's easy to delete or hardlink common assets.

venusenvy47 8mo ago
I see that it gives three choices for saving the assets: single file, zip or folder. Is the zip version just zipping the folder?
- ninalanyon 8mo ago
  I don't know, I've never tried it. I picked it because of the folder option which makes grepping for content easier and faster.

O1111OOO 8mo ago

> Have you https://addons.mozilla.org/firefox/addon/single-file/ https://addons.mozilla.org/firefox/addon/single-file/ Yes I have. I tried maff, mht, SingleFile and some others over the years. MAFF was actually my goto for many years because it was just a zip container. It felt future-proof for a long time until it wasn't (I needed to manually extract contents to view once the supporting extension was gone). I seem to recall that MHT caused me a little more of a conversion problem. It was my concern for future-proofing that eventually led me back to "Save As..". My first choice is "Save as..." these days because I just want easy long-term access to the content. The content is always the key and picking and choosing which asset to get rid of is fairly easy with this. Sometimes it's just all the JS/trackers/ads, etc.. If "Save as..." fails, I'll try 'Reader Mode' and attempt "Save as.." again (this works pretty well on many sites). As a last resort I'll use SingleFile (which I like too - I tested it on even DOS browsers from the previous century and it passed my testing). A locally saved SingleFile can be loaded into FF and I can always perform a "Save As..." on it if I wanted to for some reason (eg; smaller file, js-trackers, cleaner HTML, etc).