Retarded moment of the day goes to: Wondering why I couldn't get content scripts to load when trying to pass page content to an extension. I tried all kinds of things. Reloaded the extension a hundred times. Then it finally dawned on me: the content script is for the page (duh!) not the extension. Reloaded the tab and hey presto. <Incredibly ashamed face>.
Anyway, since moving to Pinboard I've been looking for a decent Chrome extension, but most of them just seem to be glorified bookmarklets (an exception, but I'm not interested in searching). I did however notice that one of them is on Github which just made it all too inviting to click 'Fork' and start playing.
So, I've started doing some little tweaks to load the bookmarking window in the extension popup, rather than have it opening in a separate window (there are some downsides to this approach, but this is how I like it) and it also pulls in selected text to the description field. Next on the list is fixing the Read Later option similarly so it doesn't open a new window.
As an aside, before I got into tinkering with code, but when I had just started using and being interested in open source software, I used to get a wee bit upset at 'forking'. It would annoy me that rather then "get along" and contribute to one project, people would fork and you'd be stuck choosing between two (or more) options until one developed more than the other and became the obvious choice (Inkscape and Sodipodi spring to mind). However, now I've got a bit more of a clue and what's more the advent of Git and (especially) Github really do make forking a feature; of all those Chrome extensions the easiest one to start modifying was the one on Github. And the network ensures that even if my changes never get pulled back it's still linked in some way and findable by others.