Confirmed users, Bureaucrats and Sysops emeriti
1,737
edits
Test Pilot/Wayback Machine: Difference between revisions
m
→Documentation
m (→Resources) |
m (→Documentation) |
||
| Line 34: | Line 34: | ||
Options we may want to consider include: | Options we may want to consider include: | ||
* User option of turning the feature on or off, e.g. via Preferences | |||
* Option of prompting users before taking them to archived versions of pages | |||
* Support for various 404 and broken link use cases | |||
* Option of letting users browse multiple versions of archived pages | |||
Mark Graham - Feb 18, 2016 | Mark Graham - Feb 18, 2016 | ||
| Line 53: | Line 53: | ||
While the simple case of a requested page returning a 404 is common there are a number of edge cases in which doing the "right" thing is not so straight forward. These include, but are not limited to: | While the simple case of a requested page returning a 404 is common there are a number of edge cases in which doing the "right" thing is not so straight forward. These include, but are not limited to: | ||
backed up versions of URLs that have changed ownership, or use, over time | * backed up versions of URLs that have changed ownership, or use, over time | ||
requests that return a valid page (with a result code of 200) but present a "page not found" or other site-defined error message (in effect a "soft 404") | * requests that return a valid page (with a result code of 200) but present a "page not found" or other site-defined error message (in effect a "soft 404") | ||
redirects to redirects to 404 results (we will want to direct people to the version from the Wayback Machine that is from the 1st page in the chain, not the last) | * redirects to redirects to 404 results (we will want to direct people to the version from the Wayback Machine that is from the 1st page in the chain, not the last) | ||
redirects to valid pages from the same host but not what the users expected (e.g. to the homepage of a blog as opposed a specific blog post) | * redirects to valid pages from the same host but not what the users expected (e.g. to the homepage of a blog as opposed a specific blog post) | ||
requests that fail as a result of a DNS or other network breakdown (differential between transient and long-lived DNS or other networking failures) | * requests that fail as a result of a DNS or other network breakdown (differential between transient and long-lived DNS or other networking failures) | ||
certain special caes (e.g. geocities.com) where we can expect the user will want to see the old version of a page as opposed to the otherwise valid current version | * certain special caes (e.g. geocities.com) where we can expect the user will want to see the old version of a page as opposed to the otherwise valid current version | ||
pages that contain embedded resources that can not be presented (which may or may not be available or "important" enough to offer alternatives to) | * pages that contain embedded resources that can not be presented (which may or may not be available or "important" enough to offer alternatives to) | ||
pages that have changed ownership where of the phases of ownership have involved domain parking | * pages that have changed ownership where of the phases of ownership have involved domain parking | ||
A fair amount of work remains to be done to handle these conditions, and some of this will require close collaboration with browser developers to implement the functionality and interactions we have in mind. At this point we are focused on a minimum viable extension that supports: | A fair amount of work remains to be done to handle these conditions, and some of this will require close collaboration with browser developers to implement the functionality and interactions we have in mind. At this point we are focused on a minimum viable extension that supports: | ||
Actual 404s (ignoring most of the various edge cases shown above) | * Actual 404s (ignoring most of the various edge cases shown above) | ||
Offering users the option of seeing versions of pages via from the Wayback Machine, if available | * Offering users the option of seeing versions of pages via from the Wayback Machine, if available | ||
Display of Wayback Machine versions of pages from the 1st URL in a redirect chain | * Display of Wayback Machine versions of pages from the 1st URL in a redirect chain | ||
We can add more features as we get feedback from users, gain experience with how people are using the service, and as we learn more about real-world causes for people not getting the web content they are requesting and/or expecting. | We can add more features as we get feedback from users, gain experience with how people are using the service, and as we learn more about real-world causes for people not getting the web content they are requesting and/or expecting. | ||
| Line 72: | Line 72: | ||
We are especially interesting in learning the following: | We are especially interesting in learning the following: | ||
URLs that people enter that return a 404, 503 and other defined conditions, regardless of if the user elects to request a backed-up version from the Wayback Machine | * URLs that people enter that return a 404, 503 and other defined conditions, regardless of if the user elects to request a backed-up version from the Wayback Machine | ||
End user's comments, bug reports and suggestions | * End user's comments, bug reports and suggestions | ||
Counts/time for 404s, 503, and other defined conditions | * Counts/time for 404s, 503, and other defined conditions | ||
== Meeting Notes == | == Meeting Notes == | ||