Reviews for Web Archives
Web Archives by Armin Sebastian
Review by KirkH420
Rated 4 out of 5
by KirkH420, 2 years agoIt works to some extent, I like it's ability to open all the different web archives with one click.
There is a bit of an issue with some archives. For URLs: When I click on an URL to a Microsoft.com out-dated page, the Wayback Machine will take me to Microsoft's Error404 landing page.
This URL for example:
https://www.microsoft.com/en-us/download/details.aspx?id=45885
When passed to this add-on, the Wayback Machine converts it to this page:
https://web.archive.org/web/20220328035922/https://www.microsoft.com/en-us/download/404Error.aspx
*It's landing on a Wayback Redirect page. After 5 seconds, the page gets redirected to another page.
We can see in the date is /2022-03-28-03:59:22/ and this is one of the newest snapshots created by the Archive. It's unfortunate, but The Wayback Machine continues to create snapshots of these 404 pages.
So someone might say, why don't you just use the Wayback Date-toolbar to turn back to an older date? The problem is, since your tool is finding the newest snapshots, it's returning these 404 pages. This changes the URL that we're searching for.
The API docs for the Wayback Machine says "timestamp is the timestamp to look up in Wayback. If not specified, the most recenty available capture in Wayback is returned."
The correct way to use the API is to create a link like this:
http://archive.org/wayback/available?url=https://www.microsoft.com/en-us/download/details.aspx?id=45885×tamp=20010101
*This will return a .json that contains a working "closest snapshot" URL and you can click on it.
It appears that this add-on is not using the API but is trying to manipulate URLs instead. This wont work well.
If you add the "×tamp=20010101" key, it will enable the "Return closest snapshot to the date 2001-01-01" rather than return the newest available snapshot. The downside is, you'll need to write something that will handle the .json API return data. (which shouldn't be very hard)
Doing it that way will ALWAYS return a website. Not those Error404 landing pages.
There is a bit of an issue with some archives. For URLs: When I click on an URL to a Microsoft.com out-dated page, the Wayback Machine will take me to Microsoft's Error404 landing page.
This URL for example:
https://www.microsoft.com/en-us/download/details.aspx?id=45885
When passed to this add-on, the Wayback Machine converts it to this page:
https://web.archive.org/web/20220328035922/https://www.microsoft.com/en-us/download/404Error.aspx
*It's landing on a Wayback Redirect page. After 5 seconds, the page gets redirected to another page.
We can see in the date is /2022-03-28-03:59:22/ and this is one of the newest snapshots created by the Archive. It's unfortunate, but The Wayback Machine continues to create snapshots of these 404 pages.
So someone might say, why don't you just use the Wayback Date-toolbar to turn back to an older date? The problem is, since your tool is finding the newest snapshots, it's returning these 404 pages. This changes the URL that we're searching for.
The API docs for the Wayback Machine says "timestamp is the timestamp to look up in Wayback. If not specified, the most recenty available capture in Wayback is returned."
The correct way to use the API is to create a link like this:
http://archive.org/wayback/available?url=https://www.microsoft.com/en-us/download/details.aspx?id=45885×tamp=20010101
*This will return a .json that contains a working "closest snapshot" URL and you can click on it.
It appears that this add-on is not using the API but is trying to manipulate URLs instead. This wont work well.
If you add the "×tamp=20010101" key, it will enable the "Return closest snapshot to the date 2001-01-01" rather than return the newest available snapshot. The downside is, you'll need to write something that will handle the .json API return data. (which shouldn't be very hard)
Doing it that way will ALWAYS return a website. Not those Error404 landing pages.
259 reviews
- Rated 5 out of 5by CVM$IVT, 14 hours ago
- Rated 5 out of 5by Firefox user 18282872, 21 days ago
- Rated 4 out of 5by "Quién Dijo Miedo", 25 days ago
- Rated 5 out of 5by Karam Jameel Moore, a month ago
- Rated 5 out of 5by CHKH, a month ago
- Rated 5 out of 5by ClosedLenses, a month ago
- Rated 5 out of 5by Firefox user 17650359, 2 months ago
- Rated 2 out of 5by Firefox user 17329765, 2 months agoMost of the archival services this uses are useless making the "All Search Engines" button a trap that will open a bunch of useless tabs.
- Rated 5 out of 5by GDX Tech, 2 months ago
- Rated 3 out of 5by Firefox user 18440421, 2 months ago
- Rated 5 out of 5by KitsuneKai, 2 months ago
- Rated 5 out of 5by Tuana, 2 months ago
- Rated 5 out of 5by Firefox user 16347626, 3 months ago
- Rated 4 out of 5by lin356, 3 months ago
- Rated 5 out of 5by Firefox user 16554821, 3 months agoSuper, allerdings funktioniert heute 30.04. archive.is nicht mehr. Hoffentlich nur vorrübergehend.
- Rated 5 out of 5by Firefox user 18025318, 3 months ago
- Rated 5 out of 5by Firefox user 14650745, 3 months ago
- Rated 5 out of 5by Antihero, 4 months agoEnormt hjælpsom værktøj, til nyhedsartikler, nedlagte hjemmesider mm.
Man kan ikke være heldig, 100% af tiden, men f.eks. nyhedsartikler, der er gemt bag en en betalingsvæg, eller nedlagte hjemmesider - kan ofte findes, via Wayback Machine eller Archive.is - som er de to typiske kilder, der personligt bliver brugt.
Sparer tid, penge, og sved på panden. - Rated 5 out of 5by Firefox user 18351205, 4 months ago
- Rated 5 out of 5by infirms, 4 months ago
- Rated 5 out of 5by Johnny Hash, 4 months ago
- Rated 5 out of 5by geeknik, 5 months ago
- Rated 5 out of 5by GuessWhatBBQ, 5 months ago