Jón Ragnarsson asks: "I'm loosing my mind over my bookmarks. I use 3 computers on a daily basis, and not even one of them is mobile. I have about 10 instances of browsers on them, each and every one with it's own bookmark system. I have countless times cursed when I'm at home but need some obscure bookmark on my computer at work, and just can't remember the url or phrases to find it in Google. So last night I went on a mission: I decided to think up a standard to store and retreive bookmarks. But first I deceided to search the Net just in case if somebody else had done the same thing. I typed 'bookmark protocol' in Google and behold, the fourth link mentioned the ACAP - Application Configuration Access Protocol, defined in rfc2244. So, why isn't it used?"
"It's much more than a simple bookmark storage, the RFC remarks:
The Application Configuration Access Protocol (ACAP) is designed to support remote storage and access of program option, configuration and preference information.
Probably the main reason this isn't being used is because you can't rely on every user having access to an ACAP server. Well, why not have both? Your browser could implement a mini-server until you find one that you can use. So should I suggest this to Mozilla/Microsoft/Opera? Or is there a simpler way. When Netscape was the king, I simply uploaded the bookmark file to my homepage area, it worked (more or less). And since I use browser 90% for content not on my computer I'm very likely to have net access when I'm using my browser. So could this be feasable, or am I daydreaming again?"