@freakazoid It's possible that archive.org has started shipping j/s that causes the visitor to grab the page and feed the page to archive.org. That would explain the current behaviour.