And it has the same fake excuse as usual "Since this was our first OSS project, we didn’t realize at first."
He sure discovered this new open source thing and it's very confusing. It's not like it's almost 40 years old at that point. I'll never understand people who lie like toddlers.
Sorry for your story. In those days open source is REALLY HARD. Put your github link here and we will support your project by starring you and spreading your project. You definitely need to fight back.
In a general sense, open source theft is bad, obviously. I have trouble feeling bad for this specific case though, given that it is a tool for cheating in interviews and tests.
I made an OSS tool to help you cheat on your taxes, screw your business partner, or ensure your ex wife cannot see the children. Someone stole the source and is backed by a major VC firm. Is the thought different at all or exactly the same? Just raising the question.
The difference is that the tool "cheating daddy" was specifically created for the purpose of cheating. Electricity, the Internet, and Google were not created for that purpose.
Cheating daddy's tagline is "If you're gonna cheat, cheat better".
Not that I'm in any way defending Cluely/Glass. Cluely's X bio is "cheat (noun) – an advantage so good it's unfair; rewrites the balance between effort and outcome."
Disclosure: I work at Google by my thoughts are my own.
The point is being "GPL evil" is GPL. Taking the code, not obtaining the copyright, and re-licensing it is a clear violation of copyright law and immoral.
We are not little children in the playground. Two wrongs do not make a right, and rights are most important for bad people
Things like this are why I have become disillusioned with Open Source, and why latest projects have been closed source. The GPL is a good enough idea but it is basically impossible for anyone to realistically enforce. If a corporation is selling an optimized binary, then it can be almost impossible to prove that there was any violation of the GPL without viewing the source.
Well, if you're writing open source because you want to write open source, then none of this matters. If you are worried about corporations stealing your work, that should drive you away from OSS. OSS should stay "hobbyist" for the individual developer.
If a corporation is stealing your OSS code (and violating a license) then that implies that they think your code has value, they might have paid a person to write that code but instead some hobbyist built it for free and a corporation steals it.
A few months ago, I made a pull request to LMAX Disruptor, which was merged. I was initially excited because even if my PR was simple it’s still a big project that I contributed to. But after a few minutes it occurred to me that I just did free labor for a for-profit trading company. If they merged in my code then must have thought it had some value, and I decided to dedicate my time to saving this multi million dollar company some money.
My PR there was pretty simple and only took me like 30 minutes (if that), so I am not going to cry too hard over this, but it’s just something that made me realize that if a company is going to use my work, they should pay me. I don’t think it’s wrong or weird to want to be compensated for my labor.
I am still a hobbyist. Turns out you can still be a hobbyist without sharing everything you’ve ever done on GitHub.
It only devalues labor if it's leveraged specifically to do so. You could make this argument about literally any volunteer activity, software related or otherwise. The real devaluation of labor comes from things like the "gig economy" where costs and compensation are abstracted such that companies can exploit the naivete of workers who, generally speaking, are not accustomed to things like amortization and accounting for external costs, thus significantly driving down their own labor, operational expenses, and risks by passing them directly to the workers. At least open source projects are up-front about what's to be expected, and tend not to engage in exploitative practices.
I have had a bunch of jobs. When I have wanted to use open source libraries, I have been told “no” because the repo has no recent updates, because that suggests that whomever built it isn’t working it anymore. Conversely, where there are lots of updates, the project is likely to be used.
Why am I telling this story? Because it suggests to me that companies will only use these libraries if there is a guarantee of ongoing free labor; presumably they could use an old appropriate library and pay people to fix any issues as they come up. Admittedly, I know that some companies do exactly that, and that’s great, but I do not think it’s the majority.
I don’t think the people doing Open Source are bad people at all, far from it, in fact. I think a lot of these people are very smart and hard workers, and I think they should be compensated for their work, even if they are just “hobby projects”. If my project is creating value for a company, then that company can afford to pay me.
I don’t like the gig economy either but I don’t think it’s relevant to my complaints.
Wouldn’t this still be accomplished with a freeware model? That way hobbyists could still get your stuff for free but a corporation would have a slightly more difficult time directly stealing it.
> The GPL is a good enough idea but it is basically impossible for anyone to realistically enforce.
Really? If you find a piece of proprietary software does basically the same thing as yours, and the binaries contains the same strings/artwork, then it's reasonable to make a legal case of it. You can even contact FSF and they'll take it further.
If you can directly prove a violation dead to rights (or have enough cause for a discovery request) and you have money for legal defense, sure.
A lot of open source stuff is libraries and utilities though that is pretty entrenched in the code. It is hard to even find out about a violation, let alone prove anything.
Imagine I came up with a new algorithm to do Fourier Transforms 10% faster than FFTW (or whatever the current market leader is) and make a library and I release it as GPL. A company could fairly easily just import it to whatever project they’re doing, and it would be extremely difficult for me to prove anything, especially if I don’t have any obvious things like strings in there.
That’s not even taking into account that it would be relatively easy for a corporation to just pay a junior engineer to do a direct “port” of the library to another language and pretending it’s their own independent work.
Hi everyone, this is Daniel from the Pickle team. Glass is a new open source project from us that we plan to build on and improve. We built several original features for it like live summaries, real-time STT Transcript and one-click "Ask" from summary that we're very excited about. However in initially building it we included code from a GPL-licensed project that we incorrectly attributed as Apache. This was incorrect and sloppy work on our end. We made a quick fix and are working right now to do a proper fix that addresses the issues fully and cleanly. We are sorry to the original author of the project, Soham (CheatingDaddy), and thank him for pointing this out. We are also sorry to the open source community for messing up here. Thanks everyone for caring about this.
This being on page 2 with 247 upvotes in the three hour time period this post has been up is surprising to me. I wouldn't be surprised if @dang is suppressing it (but I'd also be happy to hear that it's not being suppressed).
It's pretty spineless for the Pickle team to come out and pretend they mistakenly re-licensed GPL code. Hilarious.
> in initially building it we included code from a GPL-licensed project that we incorrectly attributed as Apache
How can you write a sentence like that in good faith?
You might have better luck if you provide a link to your code, but I rather suspect you left that out because you would probably struggle to gain sympathy from alleging the theft of https://cheatingdaddy.com/.
Honestly, I looked through both repos and while I didn't find any direct evidence for/against your assertion, it's a very boilerplate approach to connecting with LLM APIs, I don't imagine it would look much different if you both simply had similar ideas, and then used an agent to help write the code.
There's actual good reason for that. the X Formally Known As Twitter company has a content weighting system that punishes external links, regardless where the link is pointed to. So apparently Mr. Soham did the smartest thing to give that post the best chance to spread.
BTW, the X Formally Known As Twitter company is not the only one who conduced the world to this, all big names do link restriction. Look what we've become, such nice world :)
Yeah, once someone posted a link I could read, I saw that. Bummer, looks like they ripped it off and sounds like they're currently doing the usual backpedal. Sorry your project got the wrong kind of attention in this way, I also (eventually) read into your tone while reading through your repo, and I understand much of it is tongue-in-cheek. It softened my position a bit. Hope you enjoy better luck in your future endeavors.
lol, I'll bet you $10 that the name is exactly why they got themselves into this mess. Had the name been something like "meeting-agent" or some corporate friendly name like that, they probably wouldn't have tried to hide it so much.
They committed the (presumably ripped off) repo yesterday, changed the license from GPL to Apache, and now have changed it back (presumably in response to this thread).
There’s a reason they ask the question about describing a time you “hacked a system to your advantage” in the YC application. They have always selected for founders who are willing to take advantage of legal and ethical gray areas. Reddit created fake users and farmed content from Digg, Airbnb scraped listings from Craigslist.
There's an argument to be made that, even if it's an open and shut violation, if enforcement is nontrivial and a vanishingly low risk, it still pattern matches as "grey area" in terms of risk.
Not at all in favor of the person stealing someone else's code and slapping a new name on it in violation of the license, just that I think I see why people might list that as matching the same intent as a question like that.
To paraphrase Voltaire, I mean, Tallentyre, I mean, Hall, I may not agree with what you publish under the GPL but I defend to the death your right to assert the GPL...
So when someone is actively losing their rights you feel the need to go out of your way to say you're unsympathetic. What did you /intend/ to convey with this? You support them, but at this dark moment, you felt the need to kick their shins also?
It's always possible to try, especially as it seems there was a technical violation here, but whether it's worth it or likely to gain enough legal traction to yield results is another story, especially in instances of "your AI generated boiler plate looks like my AI generated boilerplate, and therefore is theft"
I’m sure there’s much more we don’t know about. They just didn’t get caught. Yc used to have this reputation of being one of the good guys but I guess nothing is really immune to corruption.
Over the last decade or two, the builder/hacker ethos has seemed to shift towards this grifter, money-over-everything attitude. I’m sure there’s a lot at play (crypto culture, VC self-selection, the attraction of ‘easy’ high salaries), but I’m sure it’ll get markedly worse with ai tooling and the any-publicity-is-good fomo marketing that’s taken over the startup scene.
My take is both OP’s tool and the blatant plagiarism of it are examples.
If it was 'just' a licensing slip up sure, but there's still a lot of integrity issues here despite that. The presentation of "we created an open source library to do X in just days" comes across as a lie right?
I feel like ycombinator leads may want to look more deeply into this one. If they are presenting it as something they've achieved that's an integrity issue right?
This is the crux of it all to me. Anyone in the industry knows mistakes happen all the time but the braggadocios nature rubs me the wrong way and spits in the face to those of YC who do indeed have integrity.
It's baffling why someone would do this tbh. It's not like the base project is some spectacular piece of engineering that would be very costly to replicate.
I'm guessing they just looked at it as a jumping point. It probably went something like:
- We know how to polish an electron app
- here is a barebone electron app with an interesting idea
- Can we build a polished UI around this, and give a demo?
The baffling part is, had they just disclosed that, no one would have given a shit. Plenty of demos begin like that: "here is a cool idea we found, here is that idea on crack". is a very common demo pattern. But of course you can't give a shout out to 'cheating-daddy' at YC demo.
It's like a fine student at a fine college, in a class they are doing fine in, then they decide to copy their friend's cover letter because "eh", then they get caught and now what? wtf would you do this?
From what I understand, it would be a breach of contract at minimum (based on what I remember from past discussions of this sort of activity involving different participants).
If someone else has a better idea of what “forking GPL 3 source code and using a different licence” would be, then please let me and others know.
Realistically this will probably just have a reputational cost for Daniel Park/Pickle. Whether he intended to or not, some amount of people will associate “pretends to make things that he did not make” with him because of this entirely unforced error.
yes, but sublicensing to even permissive ("free-er") license (GPLv3+ to Apache2.0) is a violation of license.
GPL is supposed to viral, if you are using project adopted that, you are taking the risk with it.
If you are just changing the license and took the code, that's wrong and need to get an attention. If anyone could go just yoink and relicense the GPL code to other permissive license was "legal", the https://gpl-violations.org wouldn't exist in the first place (i.e. you can just take the linux kernel code and rename it something like "mynux", redistribute in bsd-3 clause and "don't distribute the derivative part").
https://xcancel.com/soham_btw/status/1940952786491027886
This is the second time in less than a year something similar has happened.
Previously, a different YC company (Pear AI) copied Continue, changed the licenses, and "launched".
https://news.ycombinator.com/item?id=41707495
I wonder if Pear AI is dead or pivoted, their open source repos have not been updated since May.
And it has the same fake excuse as usual "Since this was our first OSS project, we didn’t realize at first."
He sure discovered this new open source thing and it's very confusing. It's not like it's almost 40 years old at that point. I'll never understand people who lie like toddlers.
Sorry for your story. In those days open source is REALLY HARD. Put your github link here and we will support your project by starring you and spreading your project. You definitely need to fight back.
Not the developer, but here is his repo:
https://github.com/sohzm/cheating-daddy
[dead]
In a general sense, open source theft is bad, obviously. I have trouble feeling bad for this specific case though, given that it is a tool for cheating in interviews and tests.
A GPL violation is a GPL violation.
I made an OSS tool to help you cheat on your taxes, screw your business partner, or ensure your ex wife cannot see the children. Someone stole the source and is backed by a major VC firm. Is the thought different at all or exactly the same? Just raising the question.
It's exactly the same of course? Why would it be different?
Google search and the internet can help you with all of those. Maybe we should ban the internet.
So can electricity.
The difference is that the tool "cheating daddy" was specifically created for the purpose of cheating. Electricity, the Internet, and Google were not created for that purpose.
Cheating daddy's tagline is "If you're gonna cheat, cheat better".
Not that I'm in any way defending Cluely/Glass. Cluely's X bio is "cheat (noun) – an advantage so good it's unfair; rewrites the balance between effort and outcome."
Disclosure: I work at Google by my thoughts are my own.
What about weapons?
The point is being "GPL evil" is GPL. Taking the code, not obtaining the copyright, and re-licensing it is a clear violation of copyright law and immoral.
We are not little children in the playground. Two wrongs do not make a right, and rights are most important for bad people
Things like this are why I have become disillusioned with Open Source, and why latest projects have been closed source. The GPL is a good enough idea but it is basically impossible for anyone to realistically enforce. If a corporation is selling an optimized binary, then it can be almost impossible to prove that there was any violation of the GPL without viewing the source.
Well, if you're writing open source because you want to write open source, then none of this matters. If you are worried about corporations stealing your work, that should drive you away from OSS. OSS should stay "hobbyist" for the individual developer.
Sure but it sort of devalues labor.
If a corporation is stealing your OSS code (and violating a license) then that implies that they think your code has value, they might have paid a person to write that code but instead some hobbyist built it for free and a corporation steals it.
A few months ago, I made a pull request to LMAX Disruptor, which was merged. I was initially excited because even if my PR was simple it’s still a big project that I contributed to. But after a few minutes it occurred to me that I just did free labor for a for-profit trading company. If they merged in my code then must have thought it had some value, and I decided to dedicate my time to saving this multi million dollar company some money.
My PR there was pretty simple and only took me like 30 minutes (if that), so I am not going to cry too hard over this, but it’s just something that made me realize that if a company is going to use my work, they should pay me. I don’t think it’s wrong or weird to want to be compensated for my labor.
I am still a hobbyist. Turns out you can still be a hobbyist without sharing everything you’ve ever done on GitHub.
It only devalues labor if it's leveraged specifically to do so. You could make this argument about literally any volunteer activity, software related or otherwise. The real devaluation of labor comes from things like the "gig economy" where costs and compensation are abstracted such that companies can exploit the naivete of workers who, generally speaking, are not accustomed to things like amortization and accounting for external costs, thus significantly driving down their own labor, operational expenses, and risks by passing them directly to the workers. At least open source projects are up-front about what's to be expected, and tend not to engage in exploitative practices.
I have had a bunch of jobs. When I have wanted to use open source libraries, I have been told “no” because the repo has no recent updates, because that suggests that whomever built it isn’t working it anymore. Conversely, where there are lots of updates, the project is likely to be used.
Why am I telling this story? Because it suggests to me that companies will only use these libraries if there is a guarantee of ongoing free labor; presumably they could use an old appropriate library and pay people to fix any issues as they come up. Admittedly, I know that some companies do exactly that, and that’s great, but I do not think it’s the majority.
I don’t think the people doing Open Source are bad people at all, far from it, in fact. I think a lot of these people are very smart and hard workers, and I think they should be compensated for their work, even if they are just “hobby projects”. If my project is creating value for a company, then that company can afford to pay me.
I don’t like the gig economy either but I don’t think it’s relevant to my complaints.
There’s a million reasons to want to write open source. A lack of attribution in particular is a killer for motivation.
i love open source because it feels like a kind of donation i can't make financially, so in a way, i'm trying to make up for that
but yeah someone claiming it all falsely isnt good for the motivation
Wouldn’t this still be accomplished with a freeware model? That way hobbyists could still get your stuff for free but a corporation would have a slightly more difficult time directly stealing it.
In general, I try to add a fingerprint into the output.
For example, in a project which generates images I usually set a specific set of pixels.
Sure, but if they have access to your code then a company could pay a junior engineer to look for any kinds of explicit fingerprints and remove it.
> The GPL is a good enough idea but it is basically impossible for anyone to realistically enforce.
Really? If you find a piece of proprietary software does basically the same thing as yours, and the binaries contains the same strings/artwork, then it's reasonable to make a legal case of it. You can even contact FSF and they'll take it further.
If you can directly prove a violation dead to rights (or have enough cause for a discovery request) and you have money for legal defense, sure.
A lot of open source stuff is libraries and utilities though that is pretty entrenched in the code. It is hard to even find out about a violation, let alone prove anything.
Imagine I came up with a new algorithm to do Fourier Transforms 10% faster than FFTW (or whatever the current market leader is) and make a library and I release it as GPL. A company could fairly easily just import it to whatever project they’re doing, and it would be extremely difficult for me to prove anything, especially if I don’t have any obvious things like strings in there.
That’s not even taking into account that it would be relatively easy for a corporation to just pay a junior engineer to do a direct “port” of the library to another language and pretending it’s their own independent work.
Hi everyone, this is Daniel from the Pickle team. Glass is a new open source project from us that we plan to build on and improve. We built several original features for it like live summaries, real-time STT Transcript and one-click "Ask" from summary that we're very excited about. However in initially building it we included code from a GPL-licensed project that we incorrectly attributed as Apache. This was incorrect and sloppy work on our end. We made a quick fix and are working right now to do a proper fix that addresses the issues fully and cleanly. We are sorry to the original author of the project, Soham (CheatingDaddy), and thank him for pointing this out. We are also sorry to the open source community for messing up here. Thanks everyone for caring about this.
The correct approach is to license your code as GPL v3 with Soham as the author. It's a simple fix.
Nice try
This being on page 2 with 247 upvotes in the three hour time period this post has been up is surprising to me. I wouldn't be surprised if @dang is suppressing it (but I'd also be happy to hear that it's not being suppressed).
It's pretty spineless for the Pickle team to come out and pretend they mistakenly re-licensed GPL code. Hilarious.
> in initially building it we included code from a GPL-licensed project that we incorrectly attributed as Apache
How can you write a sentence like that in good faith?
You might have better luck if you provide a link to your code, but I rather suspect you left that out because you would probably struggle to gain sympathy from alleging the theft of https://cheatingdaddy.com/.
Honestly, I looked through both repos and while I didn't find any direct evidence for/against your assertion, it's a very boilerplate approach to connecting with LLM APIs, I don't imagine it would look much different if you both simply had similar ideas, and then used an agent to help write the code.
If you scroll down in the xcancel link (posted in the same thread), you'll find side-by-side picture comparisons of the code, comments, libraries.
There's actual good reason for that. the X Formally Known As Twitter company has a content weighting system that punishes external links, regardless where the link is pointed to. So apparently Mr. Soham did the smartest thing to give that post the best chance to spread.
BTW, the X Formally Known As Twitter company is not the only one who conduced the world to this, all big names do link restriction. Look what we've become, such nice world :)
He includes screenshots which (to me) do indicate a certain amount of lifting.
Also the project is open source and the website is at the end of the thread. The website has a GH link in the header.
What more do you want really?
its not the best name tbh, i just made it as a meme but people take the name seriously and that hurts the case
ive posted the evidence in twitter thread link
Yeah, once someone posted a link I could read, I saw that. Bummer, looks like they ripped it off and sounds like they're currently doing the usual backpedal. Sorry your project got the wrong kind of attention in this way, I also (eventually) read into your tone while reading through your repo, and I understand much of it is tongue-in-cheek. It softened my position a bit. Hope you enjoy better luck in your future endeavors.
The appropriate thing would be to revise your initial comment.
> its not the best name tbh
lol, I'll bet you $10 that the name is exactly why they got themselves into this mess. Had the name been something like "meeting-agent" or some corporate friendly name like that, they probably wouldn't have tried to hide it so much.
If you read the post, it has examples
Today I learned about xcancel.
Maybe I’m looking at the wrong repos but both appear to be GPL-3 (or maybe it was relicensed back to original GPL-3?)
https://github.com/sohzm/cheating-daddy
https://github.com/pickle-com/glass
11 minutes ago "licensed fixed" https://github.com/pickle-com/glass/commit/5c462179acface889...
yeah he changed it rn https://github.com/pickle-com/glass/commit/5c462179acface889...
He=you? What's the game here. https://news.ycombinator.com/item?id=44460855
That's the author of this post talking about the other person changing their licensing to match.
They committed the (presumably ripped off) repo yesterday, changed the license from GPL to Apache, and now have changed it back (presumably in response to this thread).
https://github.com/pickle-com/glass/commits/main/LICENSE
What’s the context? Elon’s Twitter is really a pain, without using an account you only see the linked tweet, without the replies or anything else.
https://xcancel.com/soham_btw/status/1940952786491027886
Thanks, that’s great
There’s a reason they ask the question about describing a time you “hacked a system to your advantage” in the YC application. They have always selected for founders who are willing to take advantage of legal and ethical gray areas. Reddit created fake users and farmed content from Digg, Airbnb scraped listings from Craigslist.
There is no "grey area" here, and this isn't "hacking".
There's an argument to be made that, even if it's an open and shut violation, if enforcement is nontrivial and a vanishingly low risk, it still pattern matches as "grey area" in terms of risk.
Not at all in favor of the person stealing someone else's code and slapping a new name on it in violation of the license, just that I think I see why people might list that as matching the same intent as a question like that.
This isn't "hacking the system", though - this is an open-and-shut violation of a license with a strong legal pedigree.
not the best project but yeah still something
Hmm... a tool for cheating is stolen and relicensed by another company that specializes in cheating tools. Sort of on brand actually.
I'm having trouble mustering sympathy.
To paraphrase Voltaire, I mean, Tallentyre, I mean, Hall, I may not agree with what you publish under the GPL but I defend to the death your right to assert the GPL...
If our rights are contingent on taste then we have no rights at all.
Lacking sympathy for someone does not mean you condone them losing/lacking rights.
So when someone is actively losing their rights you feel the need to go out of your way to say you're unsympathetic. What did you /intend/ to convey with this? You support them, but at this dark moment, you felt the need to kick their shins also?
Is there a way to file lawsuits for such cases? These incidents lead to death of open-source and crush hearts of open-source developers.
I believe that BusyBox sued over violations like 17 years ago. I am not aware of any other instances.
Absolutely. The lawsuit probably wouldn't get very far when it comes to damages, however...
It's always possible to try, especially as it seems there was a technical violation here, but whether it's worth it or likely to gain enough legal traction to yield results is another story, especially in instances of "your AI generated boiler plate looks like my AI generated boilerplate, and therefore is theft"
Is this the Soham?
If you're talking about the remote work scammer in the news today, that's Soham Parekh. This is Soham Bharambe. Both are into cheating, apparently...
For those that missed it: https://techcrunch.com/2025/07/03/who-is-soham-parekh-the-se...
The Year of Soham on HN.
Soham the remote work hacker(s)*.
* The extended meaning of "hacking" is required to correctly understand this sentence.
That’s not the only corrupt stuff that yc does. There’s dreamworld.
https://www.pcgamer.com/dreamworld-infinite-world-mmo-kickst...
I’m sure there’s much more we don’t know about. They just didn’t get caught. Yc used to have this reputation of being one of the good guys but I guess nothing is really immune to corruption.
If there's not some backstory that explains this, it's actually disgusting.
disgusting behavior by an 'ai' company, say it isn't so.
Over the last decade or two, the builder/hacker ethos has seemed to shift towards this grifter, money-over-everything attitude. I’m sure there’s a lot at play (crypto culture, VC self-selection, the attraction of ‘easy’ high salaries), but I’m sure it’ll get markedly worse with ai tooling and the any-publicity-is-good fomo marketing that’s taken over the startup scene.
My take is both OP’s tool and the blatant plagiarism of it are examples.
where are we headed...
These two guys seem like they should get together.
jeers busted, everyone wins
[dead]
[flagged]
Yeah I don’t think anyone here is going to find your schtick funny either
You gave everyone permission with the license & the incentives are there. Thanks for highlighting Pickle ai's behavior.
Edit: I am wrong about the license
But… he didn’t? He used the GPLv3 license, which has other requirements. Requirements that aren’t being met by the people who forked the codebase.
But they didn’t. The company violated the GPL by re-publishing it illegally as Apache.
looks like they fixed it: https://github.com/pickle-com/glass/commit/5c462179acface889...
let's not freak out - you can't "steal" open-source code, they used an incompatible license. that was accidentally too free.
people monetizing something you open-source isn't stealing.
If it was 'just' a licensing slip up sure, but there's still a lot of integrity issues here despite that. The presentation of "we created an open source library to do X in just days" comes across as a lie right?
I feel like ycombinator leads may want to look more deeply into this one. If they are presenting it as something they've achieved that's an integrity issue right?
This is the crux of it all to me. Anyone in the industry knows mistakes happen all the time but the braggadocios nature rubs me the wrong way and spits in the face to those of YC who do indeed have integrity.
It's baffling why someone would do this tbh. It's not like the base project is some spectacular piece of engineering that would be very costly to replicate.
I'm guessing they just looked at it as a jumping point. It probably went something like:
- We know how to polish an electron app
- here is a barebone electron app with an interesting idea
- Can we build a polished UI around this, and give a demo?
The baffling part is, had they just disclosed that, no one would have given a shit. Plenty of demos begin like that: "here is a cool idea we found, here is that idea on crack". is a very common demo pattern. But of course you can't give a shout out to 'cheating-daddy' at YC demo.
It's like a fine student at a fine college, in a class they are doing fine in, then they decide to copy their friend's cover letter because "eh", then they get caught and now what? wtf would you do this?
> that was accidentally too free.
You are ignoring the fact that they claimed that they "built it in just 72 hours", accidentally omitting to mention that it's a fork of another repo.
From what I understand, it would be a breach of contract at minimum (based on what I remember from past discussions of this sort of activity involving different participants).
If someone else has a better idea of what “forking GPL 3 source code and using a different licence” would be, then please let me and others know.
Realistically this will probably just have a reputational cost for Daniel Park/Pickle. Whether he intended to or not, some amount of people will associate “pretends to make things that he did not make” with him because of this entirely unforced error.
yes, but sublicensing to even permissive ("free-er") license (GPLv3+ to Apache2.0) is a violation of license.
GPL is supposed to viral, if you are using project adopted that, you are taking the risk with it. If you are just changing the license and took the code, that's wrong and need to get an attention. If anyone could go just yoink and relicense the GPL code to other permissive license was "legal", the https://gpl-violations.org wouldn't exist in the first place (i.e. you can just take the linux kernel code and rename it something like "mynux", redistribute in bsd-3 clause and "don't distribute the derivative part").
You're ignoring the part about attribution due to copyright law, see: https://opensource.stackexchange.com/questions/13038/does-so...
Is the copyright still attributed to the original developer?
no. its BOTH attribution AND license violation.