3 ms·

I tend to just use Archive.org for this kind of thing. They've been around a long time and probably will be still around for a long time coming. http://archive.

I tend to just use Archive.org for this kind of thing. They've been around a long time and probably will be still around for a long time coming. http://archive.org/web/ http://archive.org/web/

afandian 11y ago
Does Archive.org commit to providing a persistent identifier? It's one thing having a link to the content, another having an identifier which will continue to identify the content into the future.
- kennydude 11y ago
  Yes. It uses the date in the URL
  - afandian 11y ago
    Persistent URLs can be opaque. Persistence is more about committing that, for example, the URL structures won't ever change in a backward compatible way.
    - greglindahl 11y ago
      To explain a bit better: every capture has a crawl time, that time is embedded in the WARC with that capture in it, and that's how the CDX index can refer to that page. Anyone who got our WARCs could easily present the URL structures the same way we do. That time is an essential part of the capture. We worked with others to make sure that the WARC standard does this. This is actually a really important aspect of Wayback links. Since the URL and time are always explicit in the Wayback URL, you don't have to depend on some opaque database to learn important things about that link. An archiving service that just has opaque links is like a bit.ly shortened link: you have absolutely no idea what it is if bit.ly dies.
chimeracoder 11y ago
> I tend to just use Archive.org for this kind of thing. They've been around a long time and probably will be still around for a long time coming. Except, if the domain you're archiving expires and the new owner puts up a restrictive robots.txt, archive.org will take down its archived version. Archive.org is nice for checking previous versions of websites if you need them today, but don't use them as backup with the expectation that they'll be there ten years from now.

I tend to just use Archive.org for this kind of thing. They've been around a long time and probably will be still around for a long time coming. http://archive.org/web/ http://archive.org/web/

afandian 11y ago

Does Archive.org commit to providing a persistent identifier? It's one thing having a link to the content, another having an identifier which will continue to identify the content into the future.

kennydude 11y ago
Yes. It uses the date in the URL
- afandian 11y ago
  Persistent URLs can be opaque. Persistence is more about committing that, for example, the URL structures won't ever change in a backward compatible way.
  - greglindahl 11y ago
    To explain a bit better: every capture has a crawl time, that time is embedded in the WARC with that capture in it, and that's how the CDX index can refer to that page. Anyone who got our WARCs could easily present the URL structures the same way we do. That time is an essential part of the capture. We worked with others to make sure that the WARC standard does this. This is actually a really important aspect of Wayback links. Since the URL and time are always explicit in the Wayback URL, you don't have to depend on some opaque database to learn important things about that link. An archiving service that just has opaque links is like a bit.ly shortened link: you have absolutely no idea what it is if bit.ly dies.

chimeracoder 11y ago

> I tend to just use Archive.org for this kind of thing. They've been around a long time and probably will be still around for a long time coming. Except, if the domain you're archiving expires and the new owner puts up a restrictive robots.txt, archive.org will take down its archived version. Archive.org is nice for checking previous versions of websites if you need them today, but don't use them as backup with the expectation that they'll be there ten years from now.