search

samyk / evercookie

Produces persistent, respawning "super" cookies in a browser, abusing over a dozen techniques. Its goal is to identify users after they've removed standard cookies and other privacy data such as Flash cookies (LSOs), HTML5 storage, SilverLight storage, and others.
https://samy.pl/evercookie/
4.43k stars 662 forks source link

Specify the license somewhere #42

Closed NightKev closed 8 years ago

NightKev commented 11 years ago

As far as I can tell, there's no license info anywhere. Is this public domain? GPLv3? etc...

ghost commented 11 years ago

MIT would be best.

gabrielbauman commented 11 years ago

Since there are multiple contributors, @samy cannot simply specify a license. He will need to get copyright assignment from every contributor first. Or he can get each contributor to agree to license their code under a specific license.

Public domain would be best if he doesn't care about copyright.

ghost commented 11 years ago

Easy to do, there are not many: https://github.com/samyk/evercookie/contributors

ghost commented 11 years ago

For best adoption, you need a license - the most permissive you can, which is MIT.

NightKev commented 11 years ago

Well, I think technically the "WTFPL" would be even more permissive of a license. :P Or perhaps CC0.

ghost commented 11 years ago

CC licenses often have compatibility issues. A permissive license is not only one which gives freedoms in the normal sense, but also has the greatest compatibility with other licenses, especially the copy-left variety. Without a license however, projects can be weary of using a library, so it does need to be solved.

gabrielbauman commented 11 years ago

Technically, putting code in the public domain is more permissive than any license. You only need a license if you want to maintain copyright, which @samyk will probably want to do.

MIT or 2-clause BSD would be good choices in that case.

No point in debating licenses until @samyk decides to weigh in, though. Where are you, @samyk?

NightKev commented 11 years ago

@drak The CC0 license is effectively public domain (that's the point of it), so I don't see how it could be incompatible with anything.

artob commented 11 years ago

As @NightKev mentioned, WTFPL is the most permissive possible license that still keeps the code copyrighted as such.

Public domain dedications such as CC0 or the Unlicense waive the copyright altogether, functioning as actual licenses only as a fallback strategy. See the essay Licensed, License-Free, and Unlicensed Code for more particulars.

Both Creative Commons and the Free Software Foundation recognize both CC0 and the Unlicense as valid and compatible public domain dedications, so in case you want to make the code have as few strings attached as possible, putting it in the public domain using one of them is the way to go.

dannylane commented 9 years ago

Has there been any update on the license? I can't find one anywhere and without a license specified nobody has the right to use this code in a project? Source

TPS commented 8 years ago

@samyk @NightKev "Solved" w/ https://github.com/samyk/evercookie/blob/master/LICENSE-BPL.md.

Close… FTW?

TPS commented 7 years ago

@SamyK Just FYI, & I'm sure, as per intention, that BPL confuses me completely. Did you include that license just as a commentary on "public"-source (clearly not open-source!) software, or is there a more serious purpose?