Recenzie doplnku Web Archives
Web Archives Autor: Armin Sebastian
Recenzia od používateľa KirkH420
Hodnotenie: 4 z 5
autor: KirkH420, pred 2 rokmiIt 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.
271 recenzií
- Hodnotenie: 5 z 5autor: Používateľ Firefoxu - 18606366, pred 2 dňami
- Hodnotenie: 1 z 5autor: KnOwlEdge, pred 7 dňamiBy very very VERY far THE one single most useless, ridiculous, laughable, pathetic, worthless piece of IT crap that I have EVER experienced.
It doesn't work AT ALL.
EVERY SINGLE web engine blocks it.
PATHETIC to the core. - Hodnotenie: 5 z 5autor: zeblur, pred 11 dňami
- Hodnotenie: 5 z 5autor: Používateľ Firefoxu - 18586802, pred 13 dňami
- Hodnotenie: 5 z 5autor: Používateľ Firefoxu - 18585353, pred 17 dňami
- Hodnotenie: 5 z 5autor: Používateľ Firefoxu - 16205267, pred 18 dňami
- Hodnotenie: 5 z 5autor: YoMatthewCodes, pred 20 dňami
- Hodnotenie: 5 z 5autor: Andrii, pred 24 dňami
- Hodnotenie: 5 z 5autor: Klementine Des Pêches, pred mesiacom
- Hodnotenie: 5 z 5autor: igorlogius, pred mesiacom
- Hodnotenie: 5 z 5autor: Používateľ Firefoxu - 18533204, pred 2 mesiacmi
- Hodnotenie: 5 z 5autor: CVM$IVT, pred 2 mesiacmi
- Hodnotenie: 5 z 5autor: Používateľ Firefoxu - 18282872, pred 3 mesiacmi
- Hodnotenie: 4 z 5autor: "Quién Dijo Miedo", pred 3 mesiacmi
- Hodnotenie: 5 z 5autor: Karam Jameel Moore, pred 3 mesiacmi
- Hodnotenie: 5 z 5autor: CHKH, pred 3 mesiacmi
- Hodnotenie: 5 z 5autor: ClosedLenses, pred 3 mesiacmi
- Hodnotenie: 5 z 5autor: Používateľ Firefoxu - 17650359, pred 4 mesiacmi
- Hodnotenie: 2 z 5autor: Používateľ Firefoxu - 17329765, pred 4 mesiacmiMost of the archival services this uses are useless making the "All Search Engines" button a trap that will open a bunch of useless tabs.
- Hodnotenie: 5 z 5autor: GDX Tech, pred 4 mesiacmi
- Hodnotenie: 3 z 5autor: Používateľ Firefoxu - 18440421, pred 4 mesiacmi
- Hodnotenie: 5 z 5autor: KitsuneKai, pred 4 mesiacmi
- Hodnotenie: 5 z 5autor: Елена Рогожкина, pred 4 mesiacmiимеются все необходимые функции. все отлично