Cross Browser Social Bookmarking tool with Delicious API

CelloSounds2 Dec 2008 3:18 PM
Apologies if this is one idea too many rolleyes.gif but I would love to have a social networking tool which allows me to use the same interface across multiple browsers, access my bookmarks locally like I do with my browser bookmarks, submit bookmarks from any web location easily and consistently, and customise the language used on the tool as well as the server which it points to (e.g. Delicious API pointing to a Corporate Scuttle instance with a more intranet focused naming standard rather than internet social naming... Scuttle becomes 'My Knowledge Resources' or something similarly droll rolleyes.gif ). I could then have an identical experience on intranet or internet and maybe even drag and drop bookmarks between the two, awesome.

This would provide a way to make the whole social bookmarking experience common no matter what browser I use at home at work, on my friends PC/Mac etc. An option to opt-out of persistent local storage on a particular computer (e.g in a public library etc.) would also make sense.

Any thoughts on this?

Thanks
Graham
Reply
Lloyd Hilaiel3 Dec 2008 9:57 AM
QUOTE (CelloSounds @ Dec 2 2008, 03:18 PM) <{POST_SNAPBACK}>
Apologies if this is one idea too many :rlloyd
Reply
CelloSounds3 Dec 2008 11:02 AM
QUOTE (Lloyd Hilaiel @ Dec 3 2008, 09:57 AM) <{POST_SNAPBACK}>
Yo Graham,

First: a service which allows convenient cross domain interaction with del.icio.us. That's a hearty can do.

Second: The "works on any site" part is a bit interesting. currently browserplus, by design, is restricted to page lifetime. That's to say the web page MUST opt in to using it. Now there's nothing to prevent one from writing an add-on that interacts with BrowserPlus (to, say, use the Delicious API wrappers), and a quick and dirty hack in this direction would be via greasemonkey. Imagine something that renders a customizable HTML "bottom bar" for every site you visit. It needn't be limited to social bookmarking nor need it be limited to any one site or service (buzz, del.icio.us, digg, etc).

Rolling browser lifetime functionality into the platform is something that is being talked about a lot, but it has no concrete home on our roadmap, the greasemonkey tactic might be an interesting way to experiment and flesh out use cases so that when we jump in the browser lifetime game we'd have an understanding of what specific features to tackle first.

all this make sense?

very best,;
lloyd


Lloyd,

Makes total sense. The API would be awesome, it would be much easier to develop self-contained applications that can be called from a toolbar icon or other browser chrome element whilst abstracting the main functionality of the bookmarking from the actual application itself.

Thanks!
Graham
Reply
Dado4 Dec 2008 1:15 AM
QUOTE (Lloyd Hilaiel @ Dec 3 2008, 09:57 AM) <{POST_SNAPBACK}>
Second: The "works on any site" part is a bit interesting. currently browserplus, by design, is restricted to page lifetime. That's to say the web page MUST opt in to using it. Now there's nothing to prevent one from writing an add-on that interacts with BrowserPlus (to, say, use the Delicious API wrappers), and a quick and dirty hack in this direction would be via greasemonkey. Imagine something that renders a customizable HTML "bottom bar" for every site you visit. It needn't be limited to social bookmarking nor need it be limited to any one site or service (buzz, del.icio.us, digg, etc).

Rolling browser lifetime functionality into the platform is something that is being talked about a lot, but it has no concrete home on our roadmap, the greasemonkey tactic might be an interesting way to experiment and flesh out use cases so that when we jump in the browser lifetime game we'd have an understanding of what specific features to tackle first.


browser lifetime functionality is a MUST for me. Having the ability to extend somebody else's website (e.g., Google Page Preview plugin) or write javascript code that does interesting things with any webpage (e.g., bookmarking as it was pointed out above) is something that can open up lots of exciting use cases, as opposed to just have my own page spiced up with more functionality. Greasemonkey is fine to experiment... but not viable for real deployment.

I hope you guys will put thought and weight on this idea!!!
Reply
Lloyd Hilaiel6 Dec 2008 9:26 AM
QUOTE (Dado @ Dec 4 2008, 01:15 AM) <{POST_SNAPBACK}>
browser lifetime functionality is a MUST for me. Having the ability to extend somebody else's website (e.g., Google Page Preview plugin) or write javascript code that does interesting things with any webpage (e.g., bookmarking as it was pointed out above) is something that can open up lots of exciting use cases, as opposed to just have my own page spiced up with more functionality. Greasemonkey is fine to experiment... but not viable for real deployment.

I hope you guys will put thought and weight on this idea!!!


The first step to moving to browser lifetime is identifying what features should be supported. This is a bit trickier that what we've done thus far because so far we've been taking a viable subset of what's possible in NPAPI and ActiveX and making it work everywhere. This next step would be analyzing the add-on frameworks of all browsers in existence and identifying an interesting subset there.

Javascript Injection similar to greasemonkey could be an interesting place to start. Allow services to provide a regex to match on hostname and javascript to inject?

The dangers of extending beyond what's possible with plugins is that we might have to sacrifice the ease of initial installation, and this risk is why we've prioritized other more basic features (i18n, l10n, stability, portability, and distribution size) above browser lifetime.

That point aside, it seems like the first browser lifetime features would be js injection and the ability to intercept a web request at page load time... Anything else you think would be interesting to start with?

best,
lloyd
Reply
Dado9 Dec 2008 8:15 PM
QUOTE (Lloyd Hilaiel @ Dec 6 2008, 09:26 AM) <{POST_SNAPBACK}>
That point aside, it seems like the first browser lifetime features would be js injection and the ability to intercept a web request at page load time... Anything else you think would be interesting to start with?


That would be a great start!
Reply
Anonymous29 Mar 2009 7:44 PM
QUOTE (CelloSounds @ Dec 2 2008, 03:18 PM) <{POST_SNAPBACK}>
Apologies if this is one idea too many :rGraham
Reply
Anonymous29 Mar 2009 7:47 PM
yes its a nice idea, and i am totally agree with it.

======================================

Mack

social bookmark
Reply