Closed Bug 289371 Opened 20 years ago Closed 20 years ago

Implement ability to manage "Bookmarks To Go" in bookmark manager

Categories

(Camino Graveyard :: Bookmarks, enhancement)

PowerPC
macOS
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: stefan.winopal, Assigned: mikepinkerton)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050402 Camino/0.8+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050402 Camino/0.8+ I know this feature probaply won't make it into Camino, but I think it's worth a thought. When I used Firefox today, I thought that it's nice that using the "Live Bookmarks" feature my del.icio.us bookmarks are always just one click away. Now my feature idea for Camino is, that we take "Live Bookmarks" to the next logical step, "Bookmarks To Go". What I mean is basically what Cocoalicious already does, but I think my favorite browser's bookmark pane is definitely the place where such things are supposed to happen. Camino should be able to create, edit, move and delete del.icio.us bookmarks just like local bookmarks. Personally, I'd prefer this instead of a Safari- or Firefox-like "diet" implementation of RSS. Camino shouldn't be such a copycat. Yes, Camino should definitely gain RSS support. But nothing less than a NetNewsWire class aggregator. (I know I'm chellenging ;-) Reproducible: Always Steps to Reproduce:
I'm definitely suggesting WONTFIX. Integrating with online web services isn't the best idea. RSS is a generic standard (as is Atom). But implementing this feature would involve integrating del.icio.us into the browser. What if the protocol is changed? What if the site goes down? There are so many "what ifs" that it doesn't seem worth it. Recommending WONTFIX. Keeping alive for discussion.
yeah, i don't think we should tie ourselves to edge-case bookmark tools that may go away in a year.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.