Use the Settings API instead of Bookmarks

[sindresorhus]

Issue for when the Settings API comes out of experimental status.

Would be better to save the gitmarked pages as settings, since then it won't interfere with my bookmarks. Chrome won't let me bookmark the same page in different places, and if I gitmark something, I can't bookmark it somewhere else.

[Mottie]

I was just thinking, why not just put the gitmarked data into a gist.

This is what dabblet.com does (here's an example) and thus when/if a Firefox extension is created, it will work across browsers. The only issue I can think of is if you didn't want your gitmarked pages to be publicly viewable.

[cdzombak]

Ugh, sorry about closing/reopening. Vimium keybindings just bit me...

Anyway, I'd be interested to hear @jacksonh's input on this. My 2 cents:

Gitmarks should stay in bookmarks because they are bookmarks, not settings. Using bookmarks means your Gitmarks are synched seamlessly with Chrome Sync between multiple computers.

Plus, it means they're accessible from somewhere other than the Github home page, if you just want to open one or if Github changes their home page layout and breaks the extension.

I think the problem of not being able to bookmark a project elsewhere should be solved in a different way -- perhaps Gitmarks could search your entire bookmarks tree for Github bookmarks, or something like that?

[sindresorhus]

That would work too. You can have private gists.

[sindresorhus]

@cdzombak When the extension settings sync bubbles up to stable, it will sync too, only you don't interfere with the users bookmarks.

Searching all the users bookmarks would probably work too, though I'm still leaning against settings or gist sync.