Archive.today automator

Chrome Web Store

by D. Gassner

v0.2 Updated Aug 24, 2023 8.42KiB

CWS

Users

★ 4.73

15 reviews

#1413

of 31.7K

workflow

#396 of 3.9K

⚠️Not updated in over 2 years

Description

This extension serves as a helper for archive.today users. It sanitizes the URL (stripping it of the '?' character, if existing, and everything that follows it) and then sends it to archive.today in a way which requests the most recent archived version of the URL. For example, clicking the extension's button when at https://somesite.com/home?kj345d will automatically redirect Chrome to https://archive.is/newest/https://somesite.com/home. This lets you effortlessy view the most recent archived version, and at the same time solves the problem of archive.today mistakenly thinking that your URL does not exist in their archive merely because it includes the '?' character (archive.today seems to treat each URL as unique even if the only differentiator is '?' and some subsequent characters). To use this extension, browse to the desired web page and simply click on the extension's icon. It will automatically sanitize the current URL and transfer you to archive.is, where you can view the most recent archived version of the web page, or request that the page be archived if it has not been archived yet. This extension is NOT affiliated with archive.today and is offered by me, just a fellow user of archive.today, as a tool to more easily utilize archive.today. The extension's icon is courtesy of flaticon.com. Attribution: https://www.flaticon.com/free-icons/document "Document icons created by Freepik - Flaticon"

Reviews (2 cached)

Last 12 months

★★★☆☆2025-10-25

Raj Ramesh

Needs an update to the most current archive url (.ph)

★★★☆☆2025-01-15

Zsolt Szabo

Works as advertised, with two issues: 1. Doesn't seem to handle cases like running the extension on a URL that already refers to an archive-hosted page. In this case, it simply goes to an error page instead, since archive doesn't recursively archive itself. Should instead do nothing (once it has determined that it is already accessing an archived copy). 2. Doesn't properly interact with the history stack, in that the URL for which an archived copy is to be accessed (by running the extension) is overwritten in the stack, rather than the stack pointer being incremented by one. Basically, it means the back button doesn't work, which is a problem in any case, but especially when the archive page loaded is an error page indicating that the page hasn't been archived.