@Benjol GPL would be my default choice because I like the share-left requirement but either way works for this I think. It's your project and whatever you decide, these of us contributing code just have to be fine with. And I'm good either way.
@OliverSalzburg, just tried uploading new crx to opera, says: There is a syntax error in manifest.json. Please correct it and try uploading again. The parser reported: Expecting value: line 17 column 9 (char 390)
@Caleb, maybe I screwed something up in the build?
The only specific reasons to set autocrlf to true are:
avoid git status showing all your files as modified because of the automatic eol convernsion done when cloning a unix-based eol Git repo to a Windows one (see issue 83 for instance)
and your coding tools somehow depends on a native eol styl...
It looks like the Chrome store is no longer requiring money for uploads, but that might be because I had an account from way back. I'm wondering if it wouldn't be best to get you uploading that too. It's one thing to have a bottleneck at the owner of a project, it's another to have it sideways.
In that case it's also probabaly best he does not update his version. The particular way it is broken is it has the auto-updater running pointing people back at the site home page and userscript version. That bug will actually help get people rolled over if we put an announcement on the app page about the new location.
@OliverSalzburg Your link helper comes up for me if I search for it in another browser but for the life of me I can't find it in Opera itself, which I just installed.
Aaaa, it appears to be smart enough to know it won't work with the version I installed. And how on earth is the latest Arch package for Opera 4+ major versions old?
No it's not either. I have the same version the site prompts me to download (12.16).
It appears they dropped Linux support after 12. Man I've been out of the loop.