Ask HN: A company used my source code for their product. What can I do?
Context:
- My source is a library that this company shamelessly copy/pasted into their product (whose source is also publicly available) without even giving me credit.
- This library is a core component of one of their (I would go so far to say it IS one of their) products.
- My source is publicly available BUT it's not licensed, hence it's still considered under exclusive copyright (see https://choosealicense.com/no-permission/)
- Both I and that company are in the EU.
Normally I would never enforce anything like this but we're talking about a company that was funded using public funds (Horizon 2020) and is now making money from basically selling my library.
I want to make money out of this. Any suggestions on how I should proceed? Thanks.
41 comments
[ 5.6 ms ] story [ 107 ms ] threadShitty/unethical companies do this a lot. They find clients and they pay engineers to make everything work ASAP.
Your code was a convenient way to fix everything with plausible deniability. I'm sorry for this, and I hope you do win if you sue!
If you were in the US, I would like to take a case like this on for reasonable legal rates.
Sadly, I can't obtain a law license without first paying $140,000 in mandatory tuition :) Hmmmm....
If you’re willing to live in Wyoming during law school, U of W offers free law school to anyone that gets accepted even those from out of state. The campus is super cute in a small town. If that is your thing, it’s a good deal. My brother in law took this route and he LOVED it. He moved from the east coast and plans to stay. He even convinced is girlfriend (from the east coast) to move there and now they’re married with kids.
Whether or not it reduces brain drain or whatever is irrelevant. At the end of the day, it's still theft.
I'm sure many people in developing countries wouldn't mind paying more than 5 or 10% taxes if it meant they actually got something back for their money.
Of course we need infrastructure. You don't need taxes to get it.
Here's what taxes are: You think you know what I should do with my money.
I would contact them and ask.
https://www.uwyo.edu/law/admissions/finances/
0. https://store.nolo.com/products/patent-copyright-and-tradema...
If you want a small/reasonable amount of compensation and failing that, you want them to cease using your code, I would just talk to them. Put together what your licensing terms are and then simple case of pay or stop using. This the path I would recommend, and as long as the fee is reasonable, I (as someone who has to deal with this sort of thing in my current role) would simply pay, as it the normal cost of doing business.
The reality is that this is likely the fault of a nieve developer, not the deliberate action of the organisation. Aggressively threatening to sue etc is typically overkill and the sort of behaviour that causes legal teams then to restrict developers and prevent them sharing their code etc.
>...their product (whose source is also publicly available) ...
Hacer news is not a good counseling source: you get what you pay for.
If you claim that your component IS a major part of their product and service, chances are that the European Comission might take a closer look on it.
However, you'll need a long and steady breath, as we are talking about months and years until sth. happens.
Your best option at first might be, as pointed out by others, to approach them and seek for a license agreement.
2. Courts generally move slow. It might take years before you have a positive judgement. You will likely need to sue in their jurisdiction, which puts you at a disadvantage because you do not know the language and legal procedures.
3. And this is the most important one: even if you get a positive judgement, the company is likely to be a limited liability company which can declare bankruptcy.
Did they set up an SPV (read: https://en.wikipedia.org/wiki/Special-purpose_entity) for this project, or is this a larger company with stable revenue and profits that has done this?
If at the end of the day you can collect €150,000 (as an example), you might go and collect from someone with no cash in their account. They can and will declare bankruptcy. Then you're out of pocket legal fees, with no way of recovering them, and with no compensation.
Consider this before you decide to sue.
It might be easier to just sell them the tech for a reasonable amount of money. I would not threaten to "expose" them with the H2020 programme as this might take away their source of funding -- it makes it less likely they will buy your tech.
I would reach out with a friendly email, telling them you noticed they used your library, and that you are aware they received funding because of it. Offer to sell them the library for a reasonable amount.
This idea that you own intellectual property is questionable. If someone hears your story or song or sees a picture you drew or downloads some source code then that has escaped into the wild and is no longer controlled. Given how much effort leads nowhere at all it is a kind of gift to be valued in this way.
Instead of trying to own things that are conceptual and cannot be owned it makes more sense to control release and advancement. Get people to pay up before any source code can be downloaded, and once the designs or code or whatever is out there then offer more and better to the highest and best bidders.
In general, using unlicensed software code poses a large risk for any serious company (corporations even use specialized software to check the license of every open-source project they use), so you might be able to convince them to buy a proper license from you or stop using the code. If they won't you can take legal action.
Are you speaking from experience here? Whether it has a blanket license or not has absolutely nothing to do with its status as a copyright protected work.
Quite to the opposite, having a blanket license should make it harder to determine whether its use constitutes an infringement on the copyright or is permissible by the license.
There are plenty of reasons not to give your work a blanket license. For one, you might want to share an idea without necessarily giving anyone access to use your work directly, or you may want to present the work publicly for exposure so that interested parties can license it individually.
And there are licenses for this. At the very least, a 'all rights reserved' would have been better than having nothing specified.
> Whether it has a blanket license or not has absolutely nothing to do with its status as a copyright protected work.
I never said it did. My point is, you are not helping anyone by not explicitly licensing things. You might know what rights exist if no license is specified, but not everyone does. I've seen terrible advisers and lawyers say 'well, there is no license and the source is there, so it is "open source" and fair game'. having an explicit license of rights would help to discourage all but the really dense folks from abusing it.
Legally, that phrase doesn't mean squat anywhere in the world. A copyright notice is not a license. Stating that you own the copyright to a work is not a license. It also has no bearing in the sense that you can say "all rights reserved" and still unwittingly give people implied license to use the work for, say, reading it by sharing it publicly.
> I never said it did.
You said that it would be easier to defend it in court if it was licensed. I argue on the other hand that it should be easier to defend in court if it's a clear cut copyright infringement rather than a matter of interpretation of some license, whether the license is at all enforceable and whether it's a copyright case at all and not a matter of contract law. Granting people an explicit license to your work adds a lot of moving parts.
> My point is, you are not helping anyone by not explicitly licensing things. You might know what rights exist if no license is specified, but not everyone does. I've seen terrible advisers and lawyers say 'well, there is no license and the source is there, so it is "open source" and fair game'. having an explicit license of rights would help to discourage all but the really dense folks from abusing it.
I think that someone who is dense (or more likely, unscrupulous) enough to use someone's work without a license to do so is "dense" enough to ignore the terms of a complicated license. We actually see that all the time, for example GPL licensed software being used in ways that don't comply with their license. The "open door" really happened already at sharing the code publicly at all. There will always be people that just don't give a shit.
I hate to sling negativity on the internet, but you posted code online and are upset that someone is making money off of it.
Again, I could be way off base, but you come across in a similar fashion as a patent troll looking for a payday.
This here might be a quick-and-dirty attempt to stop them, at least temporarily: https://writing.kemitchell.com/2018/09/02/Killjoy-DMCA.html
Written for the US, but shouldn't matter all that much in practice.