22120 VS SingleFile

Here. An archivist browser controller that caches everything you browse, a library server with full text search to serve your archive.

Following your "hilarious" and disrespectful answer here https://github.com/i5ik/22120/issues/63#issuecomment-7275272..., I would prefer that you remove any reference to SingleFile in the description of your project. I could not open an issue because you blocked me. And please don't accuse people without proof.

https://github.com/i5ik/22120 is a tool that archives as you browse that you can then view offline later

My solution to this (it's been done before), is to use the existing browser engine (not the system webview) installed. So far I only utilize Chrome, but as the way I connect to it is over the Chrome DevTools protocol which is somewhat fluent with the Remote Debugging Protocol[0] that Firefox is doing, this is a reasonable approach.

So far my "tool" to do this is simply a template repository with some conveniences, providing in essence a skeleton for these types of apps. I hope to flesh this out a little more, and expose a much richer API, as well as convert some of my existing popular apps (like 22120[1]) to the "framework".

The benefit of this is Graderjs has a built in 'app builder' that can create a cross-platform binary (excluding or ignoring the necessity (on MacOS) and near-necessity (on Windows) to sign your executable somehow, that lets you display your UI in JS/HTML/CSS using the already installed browser engine, as well as run code in NodeJS and using the rich APIs[2] of the browser engine itself. I'm really happy with this project and think that, even tho it's small now, it will in time become my most popular and powerful one: even bigger than my remote browser and popular web archiver.

Just give it time! :)

[0]: https://firefox-source-docs.mozilla.org/remote/index.html

[1]: https://github.com/i5ik/22120

[2]: https://chromedevtools.github.io/devtools-protocol/tot/Brows...

The GraderJS: https://github.com/i5ik/graderjs

I use this to backup pages automatically

https://github.com/i5ik/22120

Does this potentially help? https://github.com/c9fe/22120

From the blog comments, I think this is what you’re after https://github.com/c9fe/22120

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.

For small numbers of pages, the SingleFile[0] extension for Firefox (WebExtension) is pretty handy. It's not "archival quality", though, if that's the kind of "archiving" you're doing.

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