It's a valid question. It seems to me users tend to trust things which have certain level of popularity and reputation associated with them.

I personally prefer to hope for the worst. This way when nothing happens I feel extra lucky, and if bad things do happen, I feel proud of being ready for it.

I don't. In the age old debate between security and convince I sometimes want the latter and willing to ease on the former. To me being prepared for the worst is not fun. I use reputation of the software creator to manage my risks.

That could be said about nearly everything that you do.

Thank you for the heads up, I'll test it and enhance to preserve styles better.

Thanks, I'll look into making it work with pipes or some other way to interact with headless browsers.

Reach out when you do so, I've a similar use case here !

Thank you for reminding me, I need to set action="" to be an absolute path when the page is saved.

upd: Done, now forms get their action="/submit" converted into action="https://website.com/submit" when the page is saved.

Well, at least it's not called iSuck.

Thanks! Pictures should work, I'll check more tags first thing tomorrow when I start working on improving it.

I use youtube-dl for youtube and other popular web services myself. Embedding a video source as a data URL could in theory work, but it'd be quite a long base64 line. Also, editing .html files with tens or hundreds of megabytes of base64 in them would perhaps be less than convenient.

That's it in the nutshell!

It seems to work for basic pages quite well, I think that lazy load will work for most pages as long as the JavaScript is embedded (no -j flag provided) and the Internet connection is on. It saves what's there when the page is loaded, the rest is a gamble since every website implements infinite scroll differently.

Authentication is another tricky part -- it's different for every browser. I will try to convert it into a web extension of sorts, so that pages could be saved directly from the browser while the user is authenticated.

For authentication, you could add an option for passing http headers, as well as accept Netscape-style cookie files.

Whenever I want to download a video, using YouTube-dl, from a site that requires authentication, I first login using my browser and then exports the cookies using an extension.

May I ask what extension you use for cookie exporting?

Uh, I'm sorry. Please feel free to open PRs to that repo if you have anything to add or improve.

It for sure would help with those SPA websites that get their DOM fully generated by JS. A web extension that saves the current DOM tree as HTML would perhaps do a better job, especially when it comes to resources which require some web-based authentication.

This could also be an interesting alternative to PDF, especially with web fonts embedded as data URLs.

I've been using this kind of standalone PDFs produced from Markdown with pandoc for a while, and the possibilities are insane.

Imagine a paper in the form of a single HTML file, which has (a subset of) the data included, the graphs zoomable, the colors chanegable (to whatever vision problems you have) - maybe even the algorithm to play around with!

Jupyter Notebooks already go in that way. only without the single-file, open in browser aspect, I think.