ArchiveBox VS monolith

Two projects I greatly appreciate, allowing me to easily archive my bandcamp and GOG purchases (after the initial setup anyways):

https://github.com/easlice/bandcamp-downloader

https://github.com/Kalanyr/gogrepoc

And I recently learned about archivebox, which I think is going to be a fast favorite and finally let me clear out my mess of tabs/bookmarks: https://github.com/ArchiveBox/ArchiveBox

If you really want to save the content for yourself, use something like https://archivebox.io/

I've been running a local instance for a few years now and download/save tech articles all time. I can search and find them as needed.

API is coming soon (relatively, it's still a one-man project)! Stay tuned https://github.com/ArchiveBox/ArchiveBox/issues/496

I have an event-sourcing refactor in progress now to allow us to pluginize functionality like the API (similar to Home Assistant with a plugin app sotre), it will take a month or two. Next up is the REST API using the new plugin system.

I guess your best chance is to use something like https://archivebox.io/.

Yeah this is a cool project but it was discussed 2 days ago.

As mentioned by the maintainer there, they even maintain a list of alternatives, very classy:

https://github.com/ArchiveBox/ArchiveBox/wiki/Web-Archiving-...

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