search

machawk1 / Mink

Chrome extension that uses Memento to indicate that a page a user is viewing on the live web has an archived copy and to give the user access to the copy
MIT License
49 stars 3 forks source link

Provide way to run Mink logic beyond visiting the webpage and using the URI in a query #65

Open machawk1 opened 10 years ago

machawk1 commented 10 years ago

Use case, dl2014.org now forwards to http://www.city.ac.uk/ , so old site is no longer accessible through the Mink interface

machawk1 commented 10 years ago

The Omnibox API might be one method to allow the user to enter a URI without needing to navigate to the page on the live web (in the case that it doesn't exist.

https://developer.chrome.com/extensions/omnibox

machawk1 commented 8 years ago

Usage scenario:

  1. User types "Mink " or "mink://"
  2. The normal Mink logic is run with the browserAction update.
  3. On clicking the Mink icon, an HTML page from within the extension (e.g., a visualization of the TM's mementos) can be used as the background page to show the normal Mink UI.
machawk1 commented 8 years ago

Per above, using "omnibox": {"keyword" : "mink"}, in the manifest file will allow "mink " to be typed into the browser's omnibox with anything after being handled by Mink internals. We could then simply invoke the main procedure, allowing the logo to "spin" or display a separate page. The overlay on the current page might then be confusing, single the context of using the omnibox will likely be not applicable to the page in the viewport.

machawk1 commented 3 years ago

Another use case, @weiglemc's homepage that previously resided at https://cs.odu.edu/~mweigle now forwards to https://weiglemc.github.io/ . Visiting the live web page prevents mementos/TimeMaps for the origin URI-M from being considered.

Some more advance logic might be to track the redirect and use them as additional bases for querying, e.g.,

http://cs.odu.edu/~mweigle forward to https://cs.odu.edu/~mweigle/ forwards to https://weiglemc.github.io/. Visiting the first URI and following the chain on the live web might incur three queries to the aggregator for the three URI-Ms then they can be assembled on the client side, i.e., merged TimeMaps. This has some problematic nuances but could be interesting in the realm of TimeMaps with multiple URI-Ms being aggregated.

I think there has been some other work in this realm, e.g., URI-Ms for thefacebook.com and facebook.com needing to be in the same TimeMap. Thoughts @phonedude @ibnesayeed ?