Online platform’s EULA barred software developer from owning copyright in code
blog.internetcases.com
blog.internetcases.com
This was a motion to dismiss. Not a trial judgement.
Yes, it gets copyright law very wrong (you can't prevent copyright from existing by contract, you can only say who owns it, and that requires a specific written instrument).
However, the court granted leave to amend the complaint: " Ameritrade's Motion to Dismiss as to the First Counterclaim will be granted. However, leave to amend will be accorded so as to permit Mr. Matthews the opportunity to allege nonconclusory facts that explain why Mr. Matthews' alleged software modifications to TD Ameritrade's API are protected by a valid copyright."
So basically, not much to see here yet.
In any event, the summary is very clear that this was a motion to dismiss, not a trial judgment. So your critique is likely to mislead.
And yes, the court left open the option for plaintiff to replead. But I would suggest that does not do much to mitigate the extent to which the court's reasoning here as to how the agreement could limit a claim of copyright is questionable.
But thanks for your comments. I just did not feel that your word choice reflected well on our profession. Let's try to be friends anyway!
I'm not a lawyer and so can't say conclusively, but it seems to me the court isn't saying "yeah they're right you don't have copyright here" as much as they're (for the most part) saying "you didn't include enough information in the suit, come back and try again".
[1] https://docs.justia.com/cases/federal/district-courts/alaska...
I wonder if any of us could do the same if we had the code. Anyway, why should one want to use that API now?
Java API was deemed to be not copyrightable if I'm not wrong. That is not an online API but does it matter and is it a precedent? Apparently not, maybe because of the EULA. Imagine if Java came with a license saying that developers don't own their Java code. Probably we would have forgotten Java by the end of the 90s.
(At least this is how it works at the neighbour, Finland, and I think it is the same most everywhere).
But with that said, I think most stuff in an EULA wouldn't be enforceable even in a professional context. And the worst thing to happen when breaking an EULA would probably you lose your right to use the product, not whatever they wrote in the EULA.
Well, not completely. a) EULAs you are only shown on install (for paid software) have absolutely no meaning here. b) Otherwise, they count as T&Cs which are regulated and for example can't have any surprising clauses (which this probably would be)
EULAs are only valid if you get to read them before paying for the product, otherwise it would be like getting a contract without having signed it.
Then perhaps there will be enough political pressure to get the scam stopped.