Ask HN: How do you protect your open-source side projects from copycats?
10 days ago I did a Show HN post about a Chrome extension to speed up YouTube ads, which was open sourced under MIT license.
A member of HN who is also the admin of a developer community saw & commented on the project. Rather than support it as a contributor, they functionally copied it, created their own Chrome Web Store posting and shared it on r/webdev with zero acknowledgement or inclusion of the original MIT license.
I've documented in detail the whole experience.[1]
They now have an order of magnitude more traction with 10k+ users.
Although I'm happy that our project now has contributors it's hard not to think any work we do won't just continue to be copied.
Any advice would be appreciated.
[1] https://github.com/rkk3/ad-accelerator/blob/main/lessons_post.md_post.md
38 comments
[ 2.8 ms ] story [ 83.1 ms ] threadAs you point out they have an order of magnitude more users. Evidently they have some skills in marketing and distribution.
My posting hit the front page of HN and got thousands of users. Thats how they saw it & commented on it. They shared it with r/webdev which was a larger community and so got more traction. Unfortunately I didn't realize they were directly copying me until Sunday - I thought they just came to it on their own.
> Can you partner with them?
They were super hostile when I approached them.
This seems like the main mistake. Try AGPLv3 instead.
But the source is not a 1:1 copy, they functionally copied it. Although the source is very similar and derivative.
May I ask what your motivations are for open sourcing it at all?
Also I don't want to seem like I'm defending their actions, and I don't think any other commenters here are - copying your idea, directly or not, and then responding the way they did, is very toxic. But, unfortunately, this is the 'risk' one has to accept when open sourcing stuff.
I wouldn't have minded at all if they had given me a shoutout, which is all the license requires.
Ah well. It's a compliment in a way ;) Anyway I hope this doesn't discourage you from writing more free software in the future
They had the option to message me privately - they did not take that option
"I obviously probably had your idea in the back of my mind" Is what this extensions creator said when I told them it hurt my feelings they didn't even mention that they based it off of my free open source project & extension I had shared days earlier (that they commented on).
Document their timeline, versus the timeline you made and continue to make your updates.
Is there a feature you could add? Like muting the sped up ads? If you can demonstrate an "echo" of features, that'll go a long ways to proving your position.
But can you do anything about it? Not really, unless you hire a lawyer in their jurisdiction.
I had this problem back in Y2K when someone was stealing my work and not attributing it to me. They even stole the history portion, and simply cut/replaced with their name, using the exact same wording. But all I could do was annoy the hell out of them until they stopped. I actually found the customer they were dealing it off to, and informed them, using the wayback machine to prove that everything in their docs was actually my material. That finally put an end to their shenanigans.
That was just a cheeky response they gave me after I reached out on Sunday (8 days after my post).
> Document their timeline, versus the timeline you made and continue to make your updates.
They first posted theirs 4 days after my Show HN which went viral on r/webdev. I assumed they had just come to it on their own and I didn't realize they had seen & commented on my work until Sunday (8 days after the Show HN).
I mention this in the referenced post https://github.com/rkk3/ad-accelerator/blob/main/lessons_pos...
>Is there a feature you could add? Like muting the sped up ads?
Muting the ads was in the original. But in terms of another feature another member of the community contributed a PR that adds support for Hulu.
You can outcompete with power features (which is the Linux vs Windows tactic), and watch for them to suddenly get something similar in the back of their minds again.
It's unfortunate, but literally without a fully fledged legal department, your options are at street level only.
But speaking of legal action. I think of the terms: slander, libel, defamation, misleading and false accusations, and harassment.
The MIT license is for the code artifact; if you want to control the IDEA you'd need much stronger measures like a patent.
It's a small project with few LOC that they had access to and based off of. Sure they didn't just c/p but it wasn't that much more than just changing a few variable names.
"The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."
Assuming the full license (I omitted about 892 characters) were in the original the derivative work omitting the original notice violates the license. In USA, you register your copyrighted work and can sue for statutory damages.
Patent protects an original idea (reduced to practice) and one precept is that the idea got independently used only after it was disclosed to the public. Obtaining a patent from the PTO is not a trivial matter and then you can sue for your lost profits, damages based on the defendant's profits, or prohibit use by anyone. All of this assumes you really care.
I’ve shared all my source code
I think this could have been avoided entirely if you had given a shoutout to OP. It doesn’t seem like you copied their code, but it does seem like you were inspired by their idea. Open-source software is built on collaboration and recognition. Give credit where credit is due, even if it’s just a small credit.