[sed3]

I save pages into PDF files. Low tech, but works since 2001.

I print with zero page margins, so in viewer it seems like continuous page. I found Firefox produced smallest pdfs. Chrome embeds fonts and other stuff. I also use UBlock rules to hide some elements.

Pretty useful for archiving discussions on Reddit.

[bsnnkv]

> Pretty useful for archiving discussions on Reddit.

What I do now is save the comments within the discussions (on HN, Reddit, Twitter etc) as text which is indexable and searchable with additional metadata which helps for filtering (author is the main one I use), while automatically archiving the entire URLs associated with them.[1]

For me, this is the best of both worlds - quick access via fault-tolerant search and filtering to the most interesting stuff while having a snapshot archive for the full context.

[1]: https://notado.app - I've been working on this for a few years now and have posted a lot in my HN comment history and technical blogs about how I have iterated on and evolved this workflow to the point where it is now

[tannhaeuser]

I get you, but I still find it sad there's so little trust left in the web stack that even a PDF is preferable. Technically, a PDF can contain anything (bitmaps, text/glyphs without semantic ordering, even JavaScript).

[alexdbird]

I often save things as PDF. The 'export as PDF' option in Safari creates a long PDF that I find much better for reference on screen than 'printing' to PDF.

But the big flaw in this, especially for saving programming related pages, is that it loses the parts of scrollable content which is not currently in view, e.g. the ends of lines in a code block.

[DaSHacka]

> Pretty useful for archiving discussions on Reddit.

I use SingleFile for that, saves pages as a single self-contained html file. That way you can still interact with collapse comment buttons and outlinks.