3 ms·
I have the same feeling. Actually, I've seen it in real life. A company I consulted a few years ago created lots of "evergreen content." Now, they had a reason
by thatwasunusual 5y ago
I have the same feeling. Actually, I've seen it in real life. A company I consulted a few years ago created lots of "evergreen content." Now, they had a reason to do so, but...
It would be cool if archive.org (or any others) had an API that made it easy and quick to look up "first seen" timestamp for any given URL.
- jrwr 5y agoHere is the API you are looking for: -- https://archive.org/wayback/available?url=example.com×tamp=19800101 https://archive.org/wayback/available?url=example.com×t... -- this will show the oldest timestamp of a archive that the wayback has. The trick is to set the timestamp to be /really/ old and it will show the first snapshot it has.
- jrochkind1 5y agoI don't think you can tell if "the text" of the page has changed since then without manually looking though. I'm not sure how you'd solve this technically, it's probably more than just telling you if the html bytes are identical, since small changes probably happen all the time to "the same article". Or it might be good enough, because this kind of content is rarely updated at the same url?
- thatwasunusual 5y agoThat is irrelevant, at least for me. :)
- jrochkind1 5y agoWhy are you interested in when the URL was first there, but not if it has entirely different content than when it was first there?
- thatwasunusual 5y agoBecause I'm only interested in when Wayback first saw the page. Nothing magical. :)
- mark-r 5y agoI wish Wayback had an indicator for how much the page has changed from one capture to the next. A simple count of the diffs should give you a good idea.
- thatwasunusual 5y agoVery nice, and thanks for that! I'm unable to find usage rules, though.