User talk:Eggfree: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 18: Line 18:


'''Presenting the proposal'''<br>
'''Presenting the proposal'''<br>
These three steps produce a set of likely bookmark candidates, and a set of groups. We can assume there is a list of existing bookmarks. We compare the existing bookmarks against our new proposal candidates. At the beginning of each browsing session we present these cadidates to the user for a "thumbs up" or "thumbs down" (think tivo).
These three steps produce a set of likely bookmark candidates, and a set of groups. We can assume there is a list of existing bookmarks. We compare the existing bookmarks against our new proposal candidates. At the beginning of each browsing session we present these cadidates to the user for a "thumbs up" or "thumbs down" (think tivo)


Thumbs up makes it on the permanent list in the suggested group. "thumbs down" eliminates it from consideration and resets scoring for the candidate link and or cluster. no action preserves the item on the proposal list for as long the analysis of browsing habit suggest it is valid.  
Thumbs up makes it on the permanent list in the suggested group. "thumbs down" eliminates it from consideration and resets scoring for the candidate link and or cluster. no action preserves the item on the proposal list for as long the analysis of browsing habit suggest it is valid.  


* A candidate may be proposed when visiting the page, the same way warings and update notices are delivered via the yellow bar
* A candidate may be proposed when visiting the page, the same way warings and update notices are delivered via the yellow bar

Revision as of 22:46, 15 November 2005

Design Topics

This page catalogs a set of design ideas and proposals for some current projects. I include a synopsis below each.

Bookmarking This scheme sprouts from the idea that effective bookmark lists can be imputed and modified based on a users browsing habits, then proposed, rather than requiring a user to consciously maintain. The idea does not eliminate maintenance, but it puts the user in a more 'executive' approval role. Thee are three steps in this bookmarking scheme: bookmark proposal, presentation, and editing.

Proposing bookmarks

Develop a proposal of candidate links


Presenting the proposal
These three steps produce a set of likely bookmark candidates, and a set of groups. We can assume there is a list of existing bookmarks. We compare the existing bookmarks against our new proposal candidates. At the beginning of each browsing session we present these cadidates to the user for a "thumbs up" or "thumbs down" (think tivo)

Thumbs up makes it on the permanent list in the suggested group. "thumbs down" eliminates it from consideration and resets scoring for the candidate link and or cluster. no action preserves the item on the proposal list for as long the analysis of browsing habit suggest it is valid.

  • A candidate may be proposed when visiting the page, the same way warings and update notices are delivered via the yellow bar
  • A candidate list may be proposed on a bookmarks page (home page) that may do some other fancy things (see bookmark presentation)

Presenting Bookmarks

Bookmarks are conventionally shown in a drodown menu and a toolbar. I'm not suggesting we change the toolbar mechanism , but I would suggest that the menu might change to a slightly different formatting, on the asumption that the bookmark proposal system would help edit the bookmark list to a more reasonable number (n < 30) or at least help. Last but not least I see bookmark editing as happening on the start page, which could become an editable "dashboard" of links and feeds.

  • need to include dash snap *
  • need to include menu snap *

Bookmarks to sites with rss feeds

Bookmarks to site clusters (say nytimes.com) where certain subpages are dominate the history/duration scoring.

Editing Bookmarks

Outside of the mechanisms for proposing bookmarks, bookmarks would be edited on the bookmark "dashboard"