3 ms·
That's why I preface the post title with "please." I know that attribution isn't required and I can't enforce it, but pretending the original analysis doesn't e
by minimaxir 11y ago
That's why I preface the post title with "please." I know that attribution isn't required and I can't enforce it, but pretending the original analysis doesn't exist is spiteful.
- bweitzman 11y agoAre you going to continue using the MIT license in the future? Or will you use a more restrictive license to encourage people to give you more explicit attribution in the future? Just following the minimum requirements of a license may not be a nice thing to do, but if you're going to be upset because someone did something you said they could but that you didn't really want them too, I can't really sympathize.
- thieving_magpie 11y agoTotally unsolicited advice here, dismiss it if you like - consider removing the guy's full name from your posts. As you can see, people are quick to repeat it here in this thread and I'm sure elsewhere. The guy did something wrong and in your words "spiteful", being (much less) spiteful in return isn't going to make anything better. When I was a teenager I did something similar and was caught. I ripped off someone else's site design. The guy wasn't happy, but his response taught me a lot. I'm thankful he didn't put my name out there for the vigilantes of the internet to come calling and I learned to respect the work and creativity of others.
- leshow 11y agoInteresting choice of username considering that past...
- thieving_magpie 11y agoTrue, though unrelated. Here's where it comes from: https://en.wikipedia.org/wiki/La_gazza_ladra https://en.wikipedia.org/wiki/La_gazza_ladra
- jordigh 11y agoI think it's even more spiteful when you write a blog post like this when someone uses your code in the way you intended it to be used. There was no slander against you, was there? If so, that's already covered by laws other than copyright. And if you want more attribution (I'm not sure if the authors' analysis counts as a "substantial" reproduction of your own work), then use a 3-clause BSD, which says, 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. That way, any reproduction of your work that wouldn't fall under fair use requires attribtuion. I'm not sure if the "substantial" part of the MIT license is the same scope as "fair use", but without that adjective, the BSD license might be more explicit about requiring attribution. I have had my own free software used in ways I don't like, but I don't write a blog post about it. After all, I made it free. You want to insult me, mock me, satirise me, print out the source code and wipe your butt with it; go ahead. That's part of what free software must allow. Point is, require with legalese what you want people to do. It's your prerogative. Above all, don't code call copying "stealing". This is not theft. It might not even be copyright infringement. Calling it "stealing" is undue indignation that indicates that they did something worse than what you explicitly allowed.
- chaz72 11y agoNonsense. The author still has a right to call him out in public and say "this jerk lied and claimed my work as his own". He did not give that right away when he used a permissive license.
- brazzledazzle 11y agoMIT already covers the copyright attribution: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
- jordigh 11y agoIs "substantial portion" the same scope as what you would need to do under fair use?
- lazzlazzlazz 11y agoI don't think anyone was "pretending the original analysis doesn't exist". Your willingness to believe that it was a deliberate act of deception rather than a minor error (I'm not even convinced it was an error, truly) is more troubling than anything else I'm reading here. Is open source really this toxic?