What should be a developer's position that's about to release software entirely written by him/herself? Are there any legal frameworks to protect open source developers at all?
It also feels like a very discouraging time to release anything that you put a ton of effort just to get someone in minutes to steal your authorship and leave you as if you actually didn't do anything at all? Am I wrong?
If you are releasing software open source, why are you upset when someone "steals your authorship" ?
If you don't want your code copied, then don't open source it. If it bothers you that others are going to look at and "get inspired by", "make derivatives of", "copy", "fork", etc then you shouldn't be putting it out in the open.
That's not how copyleft works. You want your source to be open and the source it's part of to be open too, because at the end of the day this is not about your source this is about users being free.
lolwhat. You're effectively just saying "there are bad actors who will flagrantly disrespect your code license and therefore the law, duh. So y are u mad?"
People who care about being respected on the most basic level are not going to stick around in a community that disrespects them. I'm not the person you were responding to, but I am mad because the social contract (not to mention the legal contract) of open source has basically been destroyed, and a lot of people have poured a large portion of their life into that community based in part on the assumption of that contract being upheld. Imagine a social contract that is important to you being violated to such a degree that you cannot go back to that society.
> If you are releasing software open source, why are you upset when someone "steals your authorship" ?
because I am not releasing it into public domain, but under license that requires (for example) attribution or releasing derivative work under the same license
I think you don't understand how open source works. If you release open source software under for example the GPL you still need to comply it.
You still have to give the source back and attribution has still to be maintained of its original authors, regardless if is a fork, a derivation or whatever you want to call it.
There are situations where none of these clauses have been complied nor its violators faced any legal consequences. That's what I'm talking about.
Now on top of that you can basically instruct and LLM to generate variations of what someone released and cover that up under the excuse that is a different project when is actually not.
Because it has been generated by a computer then we go into muddy waters about if the code generated is to be considered stolen or not.
Edit: Effectively what LLMs produce is authorship and attribution dilution.
> It also feels like a very discouraging time to release anything that you put a ton of effort just to get someone in minutes to steal your authorship and leave you as if you actually didn't do anything at all? Am I wrong?
Don't worry; the "developers" who generated your code will get their own law back when they find out it's almost impossible to monetise their theft.
I'm frequently amused by the number of "developers" on HN who claim that they poured weeks or months of effort into some product, and that they are the differentiating factor, but can't see that their weeks of effort can be cloned in a few prompts once they release.
It also feels like a very discouraging time to release anything that you put a ton of effort just to get someone in minutes to steal your authorship and leave you as if you actually didn't do anything at all? Am I wrong?
If you don't want your code copied, then don't open source it. If it bothers you that others are going to look at and "get inspired by", "make derivatives of", "copy", "fork", etc then you shouldn't be putting it out in the open.
People who care about being respected on the most basic level are not going to stick around in a community that disrespects them. I'm not the person you were responding to, but I am mad because the social contract (not to mention the legal contract) of open source has basically been destroyed, and a lot of people have poured a large portion of their life into that community based in part on the assumption of that contract being upheld. Imagine a social contract that is important to you being violated to such a degree that you cannot go back to that society.
because I am not releasing it into public domain, but under license that requires (for example) attribution or releasing derivative work under the same license
You still have to give the source back and attribution has still to be maintained of its original authors, regardless if is a fork, a derivation or whatever you want to call it.
There are situations where none of these clauses have been complied nor its violators faced any legal consequences. That's what I'm talking about.
Now on top of that you can basically instruct and LLM to generate variations of what someone released and cover that up under the excuse that is a different project when is actually not.
Because it has been generated by a computer then we go into muddy waters about if the code generated is to be considered stolen or not.
Edit: Effectively what LLMs produce is authorship and attribution dilution.
Don't worry; the "developers" who generated your code will get their own law back when they find out it's almost impossible to monetise their theft.
I'm frequently amused by the number of "developers" on HN who claim that they poured weeks or months of effort into some product, and that they are the differentiating factor, but can't see that their weeks of effort can be cloned in a few prompts once they release.