Ongoing development

[God-damnit-all]

I'm a little worried to see the WebMemex projects haven't been worked on in quite some time. I know they're both considered stable, but when it comes to browser-related projects, things have a tendency to change at a pretty fast pace, to where a few years makes a very big difference.

I've been looking at freeze-dry as an alternative to using SingleFile's CLI, since it lets you save assets without converting them to embedded base64 data, which is good for making continuous backups. But this project hasn't been touched in a year and the browser extension in three years, so I'm not sure whether to invest the time in adapting my backup scripting to use freeze-dry instead or not.

Sorry to be a nag, but it would be very helpful to know. Thank you.

[Treora]

Sorry to be a nag, but it would be very helpful to know. Thank you.

Know what, exactly? :)

I’d consider Freeze-dry ready to use, but it may require an ‘early adopter attitude’ as it has not been heavily used and tested yet. I unfortunately lack time for actively developing it further at the moment, but could still spend the occasional hour for reviewing suggestions, bug-fixing, etc. if people are interested in contributing.

As for falling behind on the ever-growing overcomplexity of the web: lack of support for dynamically modified CSS (#45) and, less often, custom elements (#21) appear the main issues in my personal experience of web-archiving with the WebMemex browser extension.

Regarding the latter, this browser extension is indeed less maintained. It still needs an update to incorporate the latest freeze-dry version. I ran into some issue with its build dependencies, and figured it’s time to convert its gulp+browserify approach to use Vite instead (with vite-plugin-web-extension). Did not get to that yet..

I hope this answers your question somewhat.