Live data from Hacker News

Show HN: Mummify – Preserve web content, fight link rot

mummify.it

61–70 of 70 posts

Re: Show HN: Mummify – Preserve web content, fight link rot

#64
I use Safari web archives for a similar task.

But I wonder...isn't it safe to assume that, eventually, browser rendering engines* will change to the degree that something I saved 4+ years ago is essentially unreadable?

And doesn't that same potential problem apply to a hosted service as well?

*I'm using that vague term to describe everything I don't understand about how browsers render pages, markup, and javascript, which is a lot.

Re: Show HN: Mummify – Preserve web content, fight link rot

#65

I use Safari web archives for a similar task. But I wonder...isn't it safe to assume that, eventually, browser rendering engines* will change to the degree that something I saved 4+ years ago is essentially unreadable? And doesn't that same potential problem apply to a hosted service as well? *I'm using that vague term to describe everything I don't understand about how browsers render pages, markup, and javascript,…

I agree. I think the safest bet would be to keep a static image as well. Without a static image would will always question if the rendering engine has even slightly changed the look.

Re: Show HN: Mummify – Preserve web content, fight link rot

#66
post #50

Earlier quoted context omitted.

There already is an open source analog: http://www.archiveteam.org/index.php?title=Wget_with_WARC_ou... + http://archive.org/web/web.php

Wget is definitely a good start. What's needed is a shiny and usable UI, ways to catalog / tag / search inside your saved data, and a painless installation process. This could use come work.

I think Evernote was also intended to solve this. Unfortunately, it is also proprietary. So, there is definitely demand for this.

Re: Show HN: Mummify – Preserve web content, fight link rot

#68
post #20

Earlier quoted context omitted.

You're running an extension that purposely disables what makes the majority of the web work. Unless you disable it, you can't really complain about sites not working correctly for you.

Let's hope you never need to use a screen reader.

This is a red herring. The overwhelming majority of screen readers support javascript front ends. As in, over 98% of people who use screenreaders use one that supports javascript.

source: http://webaim.org/projects/screenreadersurvey4/#javascript

Re: Show HN: Mummify – Preserve web content, fight link rot

#69
post #65

I use Safari web archives for a similar task. But I wonder...isn't it safe to assume that, eventually, browser rendering engines* will change to the degree that something I saved 4+ years ago is essentially unreadable? And doesn't that same potential problem apply to a hosted service as well? *I'm using that vague term to describe everything I don't understand about how browsers render pages, markup, and javascript,…

I agree. I think the safest bet would be to keep a static image as well. Without a static image would will always question if the rendering engine has even slightly changed the look.

Maybe save as a PDF if it's the content you're most interested in.

Re: Show HN: Mummify – Preserve web content, fight link rot

#70
post #69
post #65

Earlier quoted context omitted.

I agree. I think the safest bet would be to keep a static image as well. Without a static image would will always question if the rendering engine has even slightly changed the look.

Maybe save as a PDF if it's the content you're most interested in.

I save screenshots for that, but when I save an archive it's usually b/c I'm interested in referencing non-static elements. Like animation, transition, responsive behavior, etc.
Post reply on HN