Revisiones de Web Archives
Web Archives por Armin Sebastian
Revisado por KirkH420
Se valoró con 4 de 5
por KirkH420, hace 3 añosIt 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.
317 revisiones
- Se valoró con 4 de 5por dost, hace 16 días
- Se valoró con 5 de 5por frostbyte, hace 18 días
- Se valoró con 5 de 5por Usuario de Firefox 19173586, hace 18 días
- Se valoró con 5 de 5por Usuario de Firefox 19114790, hace 20 días
- Se valoró con 5 de 5por Usuario de Firefox 18905802, hace 22 días
- Se valoró con 5 de 5por Usuario de Firefox 19145735, hace 22 días
- Se valoró con 5 de 5por Usuario de Firefox 19128233, hace un mes
- Se valoró con 5 de 5por casi dancasy, hace un mes
- Se valoró con 5 de 5por Usuario de Firefox 19096545, hace un mes
- Se valoró con 5 de 5por wertzuz, hace 2 meses
- Se valoró con 5 de 5por Kay, hace 2 meses
- Se valoró con 5 de 5por Kasander, hace 3 meses
- Se valoró con 5 de 5por selmasoken, hace 3 meses
- Se valoró con 1 de 5por Happy, hace 4 mesesYou're better off just manually visiting the archive websites. Here's a suggestion, instead of opening a specific snapshot, open the snapshots (or history) page where the user can see (if) different snapshots and play around till they find the one that works. This will reduce the number of times the user gets "No results"
- Se valoró con 5 de 5por BatsRule, hace 4 meses
- Se valoró con 1 de 5por Sione, hace 4 meses
- Se valoró con 5 de 5por Maximilian Grothusmann, hace 4 meses
- Se valoró con 5 de 5por Usuario de Firefox 15254436, hace 4 meses
- Se valoró con 5 de 5por Usuario de Firefox 18866863, hace 5 meses
- Se valoró con 5 de 5por Usuario de Firefox 18248595, hace 5 meses
- Se valoró con 5 de 5por VaRLoK, hace 5 meses
- Se valoró con 5 de 5por stop5, hace 5 meses
- Se valoró con 5 de 5por GothGlamPrincess, hace 5 meses
- Se valoró con 5 de 5por BillKoochooloo, hace 6 meses
- Se valoró con 5 de 5por bunnie, hace 6 meses