brajeshwar VS SingleFile

I have been on this whole journey of plain-text, longevity, legacy, and similar ideas. I recently moved my 20+ year old blog[1] to a plain-text (Markdown) and will continue to make it simpler that it should continue to last as long as it can be served out of the simplest hosting possible.

HTML in its raw form is very hard to read. I wanted something simple enough but still has some formatting[2] -- Markdown did that while I avoid spicing it up with formatting.

Right now, it is on Github and if needed, my 13-year old can edit directly there and it will update my website.

I hope that in few years, I shouldn't have to rely on Github either but, hopefully, decentralized that it is somewhere/everywhere on the Internet that it will live it as long as my domain is renewed.

1. https://brajeshwar.com/2021/brajeshwar.com-2021/

2. https://github.com/brajeshwar/brajeshwar.github.io

Something like ArchiveBox or SingleFile are in the same ballpark of tools, but both seem to eschew Safari Webarchive as a format.

https://github.com/gildas-lormeau/SingleFile?tab=readme-ov-f...

> But I don't think they're around anymore and have no idea how you could achieve similar functionality with dynamic pages anyway.

Chromium's MHTML "Save as…" and the SingleFile WebExtension should both save copies of the rendered DOM.

Apparently Safari has WebArchive and Mozilla had MAFF for similar use cases.

I think WARC is supposed to save enough data about network streams for dynamic pages to work. At least on the Wayback Machine, infinite scrolling and "Load More" buttons do kinda work sometimes. You may have to load the archived pages in a browser and try to use each dynamic feature at least once, to trigger requests for needed resources.

SingleFile: https://github.com/gildas-lormeau/SingleFile

LWN on WARC, tools: https://anarc.at/blog/2018-10-04-archiving-web-sites/

Self-hostable web archives: https://awesome-selfhosted.net/tags/archiving-and-digital-pr...

Wayback Machine addons, bookmarklets: https://help.archive.org/help/save-pages-in-the-wayback-mach...

That's interesting. I have been saving articles as PDF files, which is browser-independent, but useful just for search and reference, a nuisance to quote/copy-and-paste.

If I search only the computer, I don't get results from EBay and Amazon at the top. The idea of keeping the knowledge base separate from the primary notes is a good idea. In my case, that knowledge base is the file system, and the primary notes are whatever I choose.

When I was using Evernote, the inbox was the knowledge base and notebooks were the focus. I just had too many different potential projects going on to manage this well.

Looking to focus.

I'll revisit Firefox and SingleFile.

Explanation of the zip file inside.

https://github.com/gildas-lormeau/SingleFile/blob/master/faq...

[2] https://github.com/gildas-lormeau/SingleFile/blob/master/faq...

I agree it would be "great" a complete website in the ZIP. I think this is technically possible, someone just have to code it.

[1] https://github.com/gildas-lormeau/SingleFile#singlefile

Singlefile [1] works pretty well for me for that use case.

It has the added advantage that the file format is just plain HTML, and together with “reader mode” in most browsers, it’s a great way to save long-form text or other mostly static pages for later reference.

It obviously doesn’t work for very dynamic pages, let alone web apps.

[1] https://github.com/gildas-lormeau/SingleFile

I’ve tried all the third party services for archiving interesting things over the years but nothing beats saving everything to your local filesystem using [SingleFile](https://github.com/gildas-lormeau/SingleFile) and using a full-text search front over the directory (something like Houdahspot, for example).

If you want to save them as a file locally you could use something like SingleFile. You could also put the URL for each wiki into archive.org's Save Page Now so that anyone can access it. Either way, without scripting, you'll have to do some manual labor to get the URL for each wiki.