WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2026 Poal.co

939

As far as I can remember: In December 2012 or January 2013, the Wayback Machine started a petabox beta project or similar, where the newly indexed pages would be displayed immediately.

But that was not always the case:

Until ~December 2012, the latest indexed captures on the Wayback Machine were fromm mid-2011.

In 2012, one saved pages using liveweb.archive.org/*, the URL was shortlyweb.archive.org/record/(which still works), before it turned intoweb.archive.org/save/`.

That method passes through the current browser's user agent, but the new Save page now method (web.archive.org/save/ without URL after it) shows a submission form similarly to Archive.Today. It does not pass through the browser's user agent, and also uses an older user agent specifically for Twitter, to circumvent the progressive web app that the Wayback Machine is currently unable to capture properly.

As far as I can remember: In December 2012 or January 2013, the Wayback Machine started a *petabox* beta project or similar, where the newly indexed pages would be displayed immediately. But that was not always the case: Until ~December 2012, the latest indexed captures on the Wayback Machine were fromm mid-2011. In 2012, one saved pages using `liveweb.archive.org/*[url]*`, and later `web.archive.org/liveweb/`. In [October 2013](http://www.digitaljournal.com/article/360776), the URL was shortly `web.archive.org/record/` (which still works), before it turned into `web.archive.org/save/`. That method passes through the current browser's user agent, but the new *Save page now* method (web.archive.org/save/ without URL after it) shows a submission form similarly to Archive.Today. It does not pass through the browser's user agent, and also uses an older user agent specifically for Twitter, to circumvent the progressive web app that the Wayback Machine is currently unable to capture properly.

(post is archived)