readability-cli VS monolith

This is the project: https://gitlab.com/gardenappl/readability-cli It converts a normal webpage to a newone but with Firefox's read mode. And it can save the new page to a local file.

I already use orgmode a bit - mostly through org-roam! I have a pretty inefficient set-up where I save a webpages via SingleFileZ, then use readability-cli on it, then convert the readable output to an orgmode file. Definitely not efficient because I need to manually complete each step, but haven't bothered to try to automate it yet.

Sorry, I didn't get the question. @mozilla/readability is not the same as readability-cli, which I once contributed and packaged with node2nix.

How execute you download a webpage for archiving? I would like something that downloads a clean version of a webpage, for offline reading. I would also like the output file to be renamed using the url title. so far i am using curl -OL but i would also like the site to be parsed and made more "readable" am looking into something like readability-cli (https://gitlab.com/gardenappl/readability-cli) Thought i would ask here, to see if anyone already has something similar. tx EDIT: this‏‏‎‏‏‎‏‏‎‏‏‎­is what i ended up with https://www.reddit.com/r/commandline/comments/kao7mu/help_needed_for_script_to_download_webpages_with/

readable does a good job of cleaning/reformating cruft https://gitlab.com/gardenappl/readability-cli

Readable was new to me, and looks quite good, thanks :-) As a PSA is the project URL https://gitlab.com/gardenappl/readability-cli But in practice it's an npm install.

While running readibility-js installed from npm I am getting this error after the desired ouput. Is there any way to remove this Error from the output output?

Monolith is a CLI tool for saving complete web pages as a single HTML file.

I have never used monolith to say with any certainty, but two things in your description are worth highlighting between the goals of WARC versus the umpteen bazillion "save this one page I'm looking at as a single file" type projects:

1. WARC is designed, as a goal, to archive the request-response handshake. It does not get into the business of trying to make it easy for a browser to subsequently display that content, since that's a browser's problem

2. Using your cited project specifically, observe the number of "well, save it but ..." options <https://github.com/Y2Z/monolith#options> which is in stark contrast to the archiving goals I just spoke about. It's not a good snapshot of history if the server responded with `content-type: text/html;charset=iso-8859-1` back in the 90s but "modern tools" want everything to be UTF-8 so we'll just convert it, shall we? Bah, I don't like JavaScript, so we'll just toss that out, shall we? And so on

For 100% clarity: monolith, and similar, may work fantastic for any individual's workflow, and I'm not here to yuck anyone's yum; but I do want to highlight that all things being equal it should always be possible to derive monolith files from warc files because the warc files are (or at least have the goal of) perfect fidelity of what the exchange was. I would guess only pcap files would be of higher fidelity, but also a lot more extraneous or potentially privacy violating details

console $ nix-init default.nix -u https://github.com/Y2Z/monolith [...] (press enter to select the defaults) $ nix-build -E "(import { }).callPackage ./. { }" [...] $ result/bin/monilith --version monolith 2.7.0

For example, here’s a command-line tool to save webpages as HTML files: https://github.com/Y2Z/monolith

monolith: Convert any webpage into a single HTML file with all assets inlined.

There is also a program (monolith: https://github.com/Y2Z/monolith) that does the same

besides wget, for single pages I use monolith https://github.com/Y2Z/monolith

You can pipe the URLs through something like monolith[1].

https://github.com/Y2Z/monolith