Replying to an (inexplicably, as it was high quality) deleted comment: > I thought the same thing 10 years ago. I have(had?) many thousands of bookmarks collec

Replying to an (inexplicably, as it was high quality) deleted comment: > I thought the same thing 10 years ago. I have(had?) many thousands of bookmarks collected over 10 years. All of the most interesting things I ever read. Imagine my disappointment when I eventually realized most of them are now gone. Site is gone, URL is changed, videos taken down (so many of them it's amazing), websites weren't properly archived etc. > I tried to curl all my bookmarks for a half-assed solution but dynamic loading and unusable content presentation without running all js and saving dependencies, timestamps, replies etc makes it impossible. Even worse, it's impossible to discover something relevant when there is no search function. What you get is the page title and a URL. Usually both of them useless. I tried categorizing them and adding comments but that was a lot of work and led to me deleting stuff that are hard to categorize. I'm not a professional programmer and I'm definitely not fully aware of how modern websites work (particularly on the front end). > But if someone provided a locally run telemetry-free open-source (so it's auditable) searchable archive-as-you-browse tool that legitimately works reliably and with some kind of hard (technical) guarantee that it won't break with the next browser update, I'd pay good money for it. This is basically what DK is except, I have no guarantee as it depends on Chrome Remote Debugging Protocol (aka DevTools API.). I could hack you a guarantee by packaging it with a fixed version of Chrome (thank you for this idea I have never thought that that would be something people would give it their purchase on but thank you very much for informing me of this it's very valuable to know thank you) which would guarantee that all your sites archived up to the version of Chrome used to archive them would continue to work into the future because they worked with that version of Chrome in the first place...and then you would have access to that version of Chrome to run the archive. Aside from that we can have the hand waving heuristic argument (which is not a hard technical guarantee) that Chrome has invested a lot in puppeteer and the whole browser automation API thing is blowing up and it's very big among developers and supported by a variety of browser vendors (and on track to become a bona fide w3c standard if it's not already the web driver or web devital standard I mix up the name because there was a historical one as well) and there's lots of forks of browsers so the idea that some part of the puppeteer API (CRDP API), as in the ability to intercept requests, will go away at some point in the future seems kind of unlikely but it's not something you can guarantee. Although in the limit I think the idea of packaging it with a historical version of Chrome works because in the limit your archive size is going to be larger than the 60 to 100 MB size of the Chrome binary.