3 ms·
From the perspective of a developer using the BSD license, such as myself, this isn't such a big deal. A violation means "someone removed or replaced the copyri
by kazinator 7y ago
From the perspective of a developer using the BSD license, such as myself, this isn't such a big deal. A violation means "someone removed or replaced the copyright notice in my source code file". I don't want them to stop using or redistributing the program, including in its binary form that has no copyright notices; just restore the notices in any redistributed source.
I'm in favor of retaining only a limited form of IP law, which makes it unlawful to misrepresent the origin of a work. Basically, I would have academic misconduct and related types of misrepresentation continue to be offenses (even outside of an academic examination or publication setting), but not copying.
Other than that, scrap copyright with extreme prejudice.
Only problem is, what happens to the artists. Developers can still make money in a world in which the power of copyright is limited to fighting plagiarism. A lot of programs are in fact free to copy, but operate with limitations in the absence of a purchased license. But you can't record a song so that only limited features of the song are available for a limited time, unless the license is purchased. Such works can be taken outside of DRM easily via the analog hole.
- kube-system 7y agoWhich is why I used GPL as the example -- it requires modifications to be shared. BSD really wouldn't be affected nearly as much. If we lived in a world where all free software was more like BSD, projects would look a lot less like linux, and a lot more like this: https://en.m.wikipedia.org/wiki/Mach_(kernel%29 https://en.m.wikipedia.org/wiki/Mach_(kernel%29
- randallsquared 7y ago> I'm in favor of retaining only a limited form of IP law, which makes it unlawful to misrepresent the origin of a work. There's a technical solution (crypto signing) to that which is applicable exactly to those people who care, so it seems unnecessary to have legal machinery to enforce it.
- breck 7y agoI think this is a very good point. With git and proof of work hash patterns, it becomes not only unwise to falsely try and take credit for someone else's work, but technically infeasible to do. It's also becomes quite easy to add references (did I forget something? -- send a pull request!).