Hi Loic and everyone I had a look at IndieGogo: -> LibreJS pretty much blocks every script on all pages -> This doesn't seem to be a problem much - I'm still able to browse and look at projects -> Couldn't login with LibreJS enabled - but found https://www.indiegogo.com/accounts/sign_up seems to take care of that just fine. -> Couldn't begin or complete the "contribute" cycle, which is the critical step
BUT - even if I tweak and hack around and get IndieGogo to work in a LibreJS compliant way (I'm open to suggestions for *how* to do this exactly) - they use PayPal for payments - and PP doesn't work when LibreJS is enabled. So - any ideas on how one would override/augment the default working of IndieGogo? I'm thinking an add-on that hijacks key pages, but have never done that particularly. Other option is a bookmarklet, but this would require the user to press the "contribute in LibreJS friendly way" bookmarklet every time they'd want to get things done. And on every page in the process... Also: Who talks to PayPal? They'd be a good crowd to get onboard, and it seems they "already are" (https://www.fsf.org/news/paypal). It could just be LibreJS not playing nicely with their systems, or they just need to get compliant. Maybe RMS or someone with a gnu.org email address should get in touch with them and see what's up? I'll be getting up to speed with developing an add-on anyway, but without PP in the loop, it'd be a bit of a non starter. Shout if you need to. Thanks Ryan On Mon, Feb 17, 2014 at 2:29 PM, Loic J. Duros <[email protected]> wrote: > Hi Ryan: > > It is great that you can help with the IndieGogo stuff. Last time I > tried there was just a question about a single script which was in the > same file as the rest of the scripts, and so would prevent us from > tagging it as free. But it's been a while and I don't have access to the > emails I had back then atm. > > You can find the list of all the files/libraries that are recognized as > free directly from the source of LibreJS, although it's a good idea to > make a > documentation page for this: > > http://bzr.savannah.gnu.org/lh/librejs/dev/annotate/head:/data/script_libraries/script-libraries.json > > More of them are scheduled to be added for the next version 5.4.2 of > LibreJS, along with new functionality (the dry-run mode suggested by > John Sullivan, ...) > > Loic > > > > Ryan White <[email protected]> writes: > > > Hi Loic > > Please forgive me for mailing you directly. > > > > > > I'd like to help out with the indiegogo stuff - is there anything I > could > > do that could be useful? > > > > > > I'm downloading source for LibreJS, and will be attempting to build > as per > > the LibreJS documentation. > > > > > > I'll be poking around in the source, to try and understand what > happens > > when - your appendix B certainly sounds straightforward - but will no > > doubt have a ton of questions. > > > > > > One thing jumps to mind: Is there anywhere a matrix of javascript > > libraries that are "OK" vs ones that aren't? It might serve two > purposes: > > to advise developers on which libraries to choose initially, and to > name > > and shame the library makers that aren't on board. > > > > > > Any info much welcome. > > > > > > Thanks > > Ryan > > > > > > > > -- > > > > Ryan White > > > > > > SystemicLogic > > > > > > +27 (0) 82 875 3693 > > [email protected] > -- *Ryan White* SystemicLogic +27 (0) 82 875 3693 [email protected]
