Re:Python Library for Google Sets
by andreyf on Thursday August 13, 2009 @07:55PM
(#762026)
Sorry for nitpicking, and although I'm not sure about Latvia, (where Peter lives), in the US "no license whatsoever" certainly != "you are free to do absolutely anything you wish with the code".
Re:Python Library for Google Sets
by pkrumins on Thursday August 13, 2009 @08:15PM
(#762056)
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?
Re:Python Library for Google Sets
by cdibona on Thursday August 13, 2009 @11:27PM
(#762290)
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.
Re:Python Library for Google Sets
by pkrumins on Friday August 14, 2009 @02:25AM
(#762492)
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.
Re:Python Library for Google Sets
by andreyf on Friday August 14, 2009 @12:39AM
(#762379)
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.
Re:Python Library for Google Sets
by s-phi-nl on Thursday August 13, 2009 @08:24PM
(#762071)
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.
Re:Python Library for Google Sets
by pkrumins on Thursday August 13, 2009 @07:08PM
(#761958)
It doesn't have, and I can't think of an easy way to group them this way. Perhaps I could cook something up, like given "red, yellow, blue", do a Google Search (with my library) for each "red", "yellow", "blue" and find the surrounding words. Then count the frequencies of surrounding words, do another search at Google Sets for "red, yellow, blue", remove all those items from frequency list, and then output the most frequent word. It might be "color" or "colors". Perhaps also de-pluralize the words so that "colors == color". Just a quick idea.
mmm... might actually try it out, if it works, will write an article about it.
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?
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.
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.
[Previously discussed on HN here: http://news.ycombinator.com/item?id=652183]
mmm... might actually try it out, if it works, will write an article about it.
There's a google vid on this subject: I never did get through it but it might make more sense to you: http://www.youtube.com/watch?v=vgqWMGT9haY