Live data from Hacker News

Monit's DMCA takedown notice for Inspeqtor

github.com

31–40 of 74 posts

Re: Monit's DMCA takedown notice for Inspeqtor

#31

"Inspeqtor which is hosted at GitHub, is far from a “clean-room” implementation. This is basically a rewrite of Monit in Go" I don't understand this. How is a re-write a license violation?

It's a copyright violation if it isn't cleanroom, that means you don't get to re-license it under different terms. It will count as a derivative work under copyright law.

For what it's worth, Monit says it's not clean-room but Mike says it is (https://twitter.com/mperham/status/519165523473358848).

Re: Monit's DMCA takedown notice for Inspeqtor

#32
I'm a developer who does just enough server management to keep my systems running, and Monit is an invaluable part of the toolkit.

However, the one thing I don't like about Monit is the pseudo natural language syntax that inspeqtor surprisingly borrowed, based on which Monit raises the DMCA claim. I wonder what the general feeling about this is in the sysadmin community, and whether people would prefer a different syntax instead.

Re: Monit's DMCA takedown notice for Inspeqtor

#33

Earlier quoted context omitted.

re-writing an open source application in a different language is not a copyright violation. see Oracle v. Google.

That's correct only if the implementation was made without using the original implementation - for example, made off of a common specification, or using only the inputs and outputs of the application. (AKA, a "clean room" implementation) If the reimplementation was made by perusing the original, it can be considered a derivative work subject to copyright.

How would you ever prove "perusing the original" conclusively?

Sure you could say "so and so downloaded Monit using IP address of 127.0.0.1 at this time", but I don't think that really is legally conclusive.

Unless the alleged violator actually posted public comments about "perusing" the original source code there's not a lot you could do. Unless you do discovery on all of his computers and he didn't delete the Monit source code. To go through all that trouble for a copyright violation on free, open source software seems hardly worth it.

Re: Monit's DMCA takedown notice for Inspeqtor

#34
Monit is wining this discussion because their DMCA notice has caused the code not be visible, since anyone with both codebases could easily look at them and see that Inspeqtor is not a translation of the Monit code in any shape or form.

Because of this, I have put the code back up, please consult https://github.com/evanphx/inspeqtor vs http://mmonit.com/monit/dist/monit-5.9.tar.gz

Re: Monit's DMCA takedown notice for Inspeqtor

#35
post #13

Earlier quoted context omitted.

What parts of the statements made in the DMCA request are wrong?

re-writing an open source application in a different language is not a copyright violation. see Oracle v. Google.

You might want to find a different example until it is settled. From the wikipedia article on the matter Oracle currently is currently winning From wikipedia: the judgement was released on May 9, 2014. The circuit court reversed the district court on the central issue, holding that the "structure, sequence and organization" of an API was copyrightable. It also ruled for Oracle regarding the small amount of literal copying, holding that it was not de minimis. The case was remanded back to the district court for reconsideration of the fair use defense

Re: Monit's DMCA takedown notice for Inspeqtor

#36
The timing of this seems odd to me. Why now, of all times? Is Inspeqtor getting too big or stealing too many Monit customers?

It's also a little strange that the tweet Monit references as being demonstrative of intent happened six months ago [0]. If that was really the issue, shouldn't they have issued the DMCA takedown then, instead of waiting so long?

I think we have about 24 hours before the DMCA's version of the Streisand effect kicks in.

[0]: https://twitter.com/mperham/status/452160352940064768

Re: Monit's DMCA takedown notice for Inspeqtor

#37
post #34

Monit is wining this discussion because their DMCA notice has caused the code not be visible, since anyone with both codebases could easily look at them and see that Inspeqtor is not a translation of the Monit code in any shape or form. Because of this, I have put the code back up, please consult https://github.com/evanphx/inspeqtor vs http://mmonit.com/monit/dist/monit-5.9.tar.gz

The title on your repro currently says "DCMA comparison".

Re: Monit's DMCA takedown notice for Inspeqtor

#38
post #37
post #34

Monit is wining this discussion because their DMCA notice has caused the code not be visible, since anyone with both codebases could easily look at them and see that Inspeqtor is not a translation of the Monit code in any shape or form. Because of this, I have put the code back up, please consult https://github.com/evanphx/inspeqtor vs http://mmonit.com/monit/dist/monit-5.9.tar.gz

The title on your repro currently says "DCMA comparison".

Thanks, fixed!

Re: Monit's DMCA takedown notice for Inspeqtor

#39

Earlier quoted context omitted.

That's correct only if the implementation was made without using the original implementation - for example, made off of a common specification, or using only the inputs and outputs of the application. (AKA, a "clean room" implementation) If the reimplementation was made by perusing the original, it can be considered a derivative work subject to copyright.

How would you ever prove "perusing the original" conclusively? Sure you could say "so and so downloaded Monit using IP address of 127.0.0.1 at this time", but I don't think that really is legally conclusive. Unless the alleged violator actually posted public comments about "perusing" the original source code there's not a lot you could do. Unless you do discovery on all of his computers and he didn't delete the Monit…

Things are seldom "proven" in court the way they are in mathematics. Instead, Mike would swear that he had never looked at the source code, which, if his lawyer is any good, he will only let him do if it's actually true, because it would open him up to perjury charges. Later, if Monit had evidence this wasn't true, they would present it. IANAL.

Re: Monit's DMCA takedown notice for Inspeqtor

#40

Well, I certainly will not be using Monit ever again should this be accurate. There is no illegal activity from what I can tell, so it's entirely baseless. Are they unclear about what copyright means? Did they hire a lawyer? Does not inspire a lot of confidence. edit: I've reached out to Monit for an explanation, and will amend if they reply.

Are they unclear about what copyright means? Something I've learned over the years is that, when it comes to legal issues, things are rarely black and white. In this case, whether or not Inspeqtr should be required to adhere to the AGPL probably comes down to whether or not it is legally a "derived work". And I'm going to go out on a limb and guess that there isn't a large body of case law covering the situation wher…

Fair enough point, though I don't feel this is a gray area. The chilling effect alone, being that I could be sued for simply looking at open source code is disturbing. Because that's what it boils down to. Most of our software today is a derivative work of something. I looked at rails code, so does that mean I can never write a web framework lest I be sued?
Post reply on HN