3 ms·

Thanks for the comment. What I have in mind is that there is no license, none, it's public, free code. Doesn't belong to anyone. Anyonce can take it and use it

Thanks for the comment. What I have in mind is that there is no license, none, it's public, free code. Doesn't belong to anyone. Anyonce can take it and use it any way they wish. What do you suggest I write instead to make this point correctly?

s-phi-nl 17y ago
I am not a lawyer, nor have I ever published code under any license, but I believe that, to let anyone do whatever they like with your code, you say that it is in the public domain.
aristus 17y ago
"Dedicated to the public domain" creativecommons.org/licenses/publicdomain/
- outotrai 17y ago
  This is probably the best option, but the FSF-approved WTFPL (Do What The Fuck You Want To Public License) may be clearer. [Previously discussed on HN here: http://news.ycombinator.com/item?id=652183 http://news.ycombinator.com/item?id=652183]
cdibona 17y ago
Honestly, pick a proper open source license like apache to protect yourself (no-warranty clause) and your users (explicit patent and copyright grant). Also, as you are latvian, under Wipo, you are essentially unable to give something away without a license due to the moral rights clause. I mean you can, but no one has a right to use it unless you explicitly grant it. You cannot disclaim rights and place it into the true public domain. Also, scraping is bad, m'kay.
- andreyf 17y ago
  scraping is bad, m'kay To the contrary, I think scraping is part of the original smalltalk OOP vision, where objects are entities universally accessible, without limitations on who/what/how they are being seen/edited.
  - seiji 17y ago
    I think he outranks you when talking about scraping google contents: http://en.wikipedia.org/wiki/Chris_DiBona http://en.wikipedia.org/wiki/Chris_DiBona
- pkrumins 17y ago
  Thanks for the suggestion. I'll choose a better license! I agree that scraping is bad, but there was no other easy way to do what I wanted (the english improvement program that I talk about in the article), so I had to write this code.

s-phi-nl 17y ago

I am not a lawyer, nor have I ever published code under any license, but I believe that, to let anyone do whatever they like with your code, you say that it is in the public domain.

aristus 17y ago

"Dedicated to the public domain" creativecommons.org/licenses/publicdomain/

outotrai 17y ago
This is probably the best option, but the FSF-approved WTFPL (Do What The Fuck You Want To Public License) may be clearer. [Previously discussed on HN here: http://news.ycombinator.com/item?id=652183 http://news.ycombinator.com/item?id=652183]

cdibona 17y ago

Honestly, pick a proper open source license like apache to protect yourself (no-warranty clause) and your users (explicit patent and copyright grant). Also, as you are latvian, under Wipo, you are essentially unable to give something away without a license due to the moral rights clause. I mean you can, but no one has a right to use it unless you explicitly grant it. You cannot disclaim rights and place it into the true public domain. Also, scraping is bad, m'kay.

andreyf 17y ago
scraping is bad, m'kay To the contrary, I think scraping is part of the original smalltalk OOP vision, where objects are entities universally accessible, without limitations on who/what/how they are being seen/edited.
- seiji 17y ago
  I think he outranks you when talking about scraping google contents: http://en.wikipedia.org/wiki/Chris_DiBona http://en.wikipedia.org/wiki/Chris_DiBona
pkrumins 17y ago
Thanks for the suggestion. I'll choose a better license! I agree that scraping is bad, but there was no other easy way to do what I wanted (the english improvement program that I talk about in the article), so I had to write this code.