thedaywefightback.js

Question: What is going to happen with the script after the campaign? https://github.com/tfrce/thedaywefightback.js/issues/98 My personal view: I still don't get why it is bad, #pleasesurveilme --> https://twitter.com/stefek99/status/433307672838819840

It's opensource, check it out: https://github.com/tfrce/thedaywefightback.js

https://github.com/tfrce/thedaywefightback https://github.com/tfrce/thedaywefightback.js

All of the people who built the site and the banner are volunteers who met on HN across various threads, and not members of any of the advocacy orgs or companies listed on the site. We're really interested in getting feedback on how future campaigns can be better, and happy to discuss some of the decisions we made. The non-profits involved did all the legal and organization lifting, and this is a great opportunity to donate to the EFF and Demand Progress if you haven't recently. Likely the most impactful thing you can do right now is to add the banner to your own site and ask the companies you work for to do the same. We've tried to make it as easy as possible to add the banner; you can find all the options (including a Cloudflare app and Wordpress plugins) here: https://github.com/tfrce/thedaywefightback.js Pushing for technical solution

So that license was suggested by someone at FSF and I ran with it because I don't know enough about licensing. Can someone who does make a suggestion and I'll change it? We do use snippets in the code from other GPL/Apache licensed code in main.js for example, but we specify the sources and licenses for each snippet in the code. My original thought was to use http://unlicense.org/. Would that work? Do I need any other language in there to clarify that the licenses of the snippets we use stand? (Feel free to submit a pull-request with fixes) Edit: Made an issue for this -> https://github.com/tfrce/thedaywefightback.js/issues/31