Reviews for Web Archives
Web Archives by Armin Sebastian
271 reviews
- Rated 1 out of 5by Sajid, 2 years ago
- Rated 4 out of 5by Firefox user 14389981, 2 years ago
- Rated 5 out of 5by rsz, 2 years ago
- Rated 4 out of 5by 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. - Rated 5 out of 5by Firefox user 17403381, 2 years ago
- Rated 1 out of 5by linda, 2 years ago
- Rated 4 out of 5by Sloping, 2 years ago
- Rated 1 out of 5by t9anef, 2 years ago
- Rated 5 out of 5by Crook, 2 years ago
- Rated 5 out of 5by Firefox user 17365597, 2 years ago
- Rated 5 out of 5by REDFOX, 2 years ago
- Rated 5 out of 5by Zodd, 2 years ago
- Rated 5 out of 5by Usuário FF 17151627, 3 years ago
- Rated 4 out of 5by Firefox user 14604821, 3 years ago
- Rated 5 out of 5by 朱钰骏, 3 years ago
- Rated 5 out of 5by CrinEx, 3 years ago
- Rated 5 out of 5by Drino955, 3 years agoEN:
Highly recommended, best of its kind, tested by mozzila and open source. Updated regularly.
RU:
Рекомендую, лучшее в своем роде, проверено mozzila и с открытым исходным кодом. Регулярно обновляется. - Rated 5 out of 5by ammar, 3 years ago
- Rated 5 out of 5by Liamb135, 3 years ago
- Rated 5 out of 5by botultest1, 3 years ago
- Rated 5 out of 5by Perkasamedika, 3 years ago
- Rated 4 out of 5by Петр, 3 years ago