For each site in my history, create a profile of the types of pages on the site (esp. looking for article type pages). For each page type, try and predict which link is the "NEXT" link. Highlight those links, and provide me with a keyboard shortcut to get there. So when I am reading NYT (etc) articles, all I do is hit CTRL-SPACE or some such in order to continue to the next page. The system should learn from my behavior, and should be directly teachable ("this is the NEXT link") as well. The criteria for determining the next link on a new site should be informed by the evolving criteria from existing sites.
For anyone doing development work, the Live HTTP headers plugin is a godsend.
It is what it says; you'll see the full text of the HTTP headers back and forth with the server. Cookies, content-type, redirects, mystery forms, you name, just throw Live HTTP at it.
Slashdot Mirror
For each site in my history, create a profile of the types of pages on the site (esp. looking for article type pages). For each page type, try and predict which link is the "NEXT" link. Highlight those links, and provide me with a keyboard shortcut to get there. So when I am reading NYT (etc) articles, all I do is hit CTRL-SPACE or some such in order to continue to the next page. The system should learn from my behavior, and should be directly teachable ("this is the NEXT link") as well. The criteria for determining the next link on a new site should be informed by the evolving criteria from existing sites.
Now that would be useful.
For anyone doing development work, the Live HTTP headers plugin is a godsend.
It is what it says; you'll see the full text of the HTTP headers back and forth with the server. Cookies, content-type, redirects, mystery forms, you name, just throw Live HTTP at it.