1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
Another example could be clean room design. Essentially reverse engineering code without using copyrighted code. Having someone on a team who has reviewed leaked code could compromise a project and make it more likely to be hit with a copyright claim if they slip up.
This has been an issue/topic of debate with multiple open source projects such as ReactOS.
I could be slightly off here but this is my understanding of it. I hope someone corrects me if I'm off base.
Yeah this was something else I was thinking of. I'm not exactly sure about the mechanics of the infringement here, but it seems like simply knowing a thing taints you for producing a work. I guess it's more about ease of proving?
The key here is that it taints you, not the thing. Just because the source code of eg.: Acrobat is known because the source is leaked, that does not make the source code of an alternative instantly illegal.
I think the closest you can get to that is illegal numbers