code-research-object

Thanks for the reply and the links. The approach taken by Robust links is close to what I had in mind in regards to actually archiving the content. Looks like its a good solution to content drift and it's more passive than webcite. The timestamp benefit is also great. Maybe you could also include some sort of hash on the local end so maybe users could see at a glance if the nearest archive differs at all. Of course that's limited since it uses external archives and might not work with dynamically generated pages. I'll have to check out your comment [0], which seems like a lot of thought went into it, and the research paper. [0]: https://github.com/mozillascience/code-research-object/issue...