Whether this was a joke or a backtracking, or this dared waste your oh so precious time- You're missing the forest for the trees. There's extreme covert and even overt hostility between how people stand on AI's gluttonous usage of the commons.
We're about to waltz into a deep period of tension between developers, and people who, empowered by multimillion dollars corporations, bravely violate developers' copyrights in the hopes of replacing their jobs, while bullying these same developers who dare express their discontent.
Developers never had "intellectual property". Under capitalism, only billion-dollar corporations do. So the problem with AI isn't that it violated some license. The real problems are that people are losing jobs, that the Internet and our community gets clogged up with more low-effort slop competing for our attention than ever before, and that the products we are all forced to use are becoming worse because corporations are trying to shove AI-features into them and put quotas on engineers to vibe-code as much as possible. There are definitely others. "Copyright" is not even scratching the surface of real problems with LLMs, and many of the people leading the charge in pointing out the evil and hypocrisy of AI companies are themselves copyright abolitionists.
This is interesting because it’s also one of SQLite’s monetizations. SQLite is in the public domain, but you need a commercial license to access their TH3 test harness with 100% branch coverage used to validate SQLite on different platforms.
Well that's embarrassing! I reported it as if it wasn't a joke. I thought the joke issue was this one about translating everything to Chinese: https://github.com/tldraw/tldraw/issues/8092
Why would they go to all the trouble of summarising the test counts in the context and writing out the full removal scope across two comment posts as a "joke"?
I'd believe it was a joke if was a one-liner but this has far more detail then that.
this issue was more of a joke (am I allowed to do that?)
Not really a fan of the qualification here to possibly scare people off from calling them out either.
To clear, I have no problem with them hiding the repo, I have no problem with them changing their mind after the blowback, but it's frustrating when they can't own these decisions and try to hide behind it being a "joke".
The headline should be changed, because it is moving from one closed source repo to another closed source repo, and on HN misleading headlines tend to be corrected even if they're deliberate on the part of the authors.
simonw correctly describes it as "not technically open source" - though OSI doesn't have the trademark, the term open source, capitalized or not, refers to the what the Open Source Definition codifies. There are other terms such as shared source, for this sort of stuff.
The headline should be changed because it was a joke: “Sorry folks, this issue was more of a joke (am I allowed to do that?) but I'll keep the issue open since there's some discussion here.”
The "this wasted my time" comments are missing the point...
In addition to his great sense of humor, Steve is usually ahead of the curve in terms of trends. There's a lesson in this. LLMs have become incredible constraint solvers ("SAT-solvers for code"). Well-thought-out tests, types, specs, and docs are all incredibly valuable constraints. This has big implications - for example what happens to licenses when you can cheaply rewrite the codebase and therefore unencumber it.
Is it really re-writing - legally - if you are starting from the codebase itself? Not a lawyer, am wondering however if the Google vs Oracle Java lawsuit has some implications for this.
This is concerning, it feels a bit tragedy-of-the-commons I suppose where having public tests are a valuable public good, thought I can't quite get the analogy straight in my head.
> feels a bit tragedy-of-the-commons ... I can't quite get the analogy straight in my head
I have a personal theory that "tragedy of the commons" has a very specific meaning, and beyond this meaning it just adds confusion. This isn't your fault - it's an overused phrase.
I'd try to examine the root of your discomfort. Why does it make you feel bad? Avoid thinking about "big ideas" like the commons or the public good.
I'm thinking of migrating to ExcaliDraw or Xournal++ next time I need a whiteboard.
The performative closing of public contributions citing the slop scare felt disingenuous from the start. You couldn't be bothered to implement _any_ mitigations that leave the community engaged with the project?
Writing a contributor karma bot, moving to a non-social or obscure git forge (most slop contributors are resume farming and GitHub is the only forge the HR cares about), newbie-unfriendly non-public workflows like git send-mail, or references from Discord... This isn't an AGI on the other side of the screen, planning the perfect strategy to infiltrate your project; it's a sub-script-kiddie trying to fill a portfolio with quick "contributions" doing the more annoying version of "fixing typos" in docs.
alt187|3 days ago
We're about to waltz into a deep period of tension between developers, and people who, empowered by multimillion dollars corporations, bravely violate developers' copyrights in the hopes of replacing their jobs, while bullying these same developers who dare express their discontent.
This is not gonna end well.
Antibabelic|3 days ago
hellcow|3 days ago
OptionOfT|2 days ago
Source: https://corecursive.com/066-sqlite-with-richard-hipp/
HN Discussion: https://news.ycombinator.com/item?id=27718701
kilroy123|3 days ago
latchkey|3 days ago
"Sorry folks, this issue was more of a joke (am I allowed to do that?) but I'll keep the issue open since there's some discussion here."
simonw|3 days ago
Well that's embarrassing! I reported it as if it wasn't a joke. I thought the joke issue was this one about translating everything to Chinese: https://github.com/tldraw/tldraw/issues/8092
cube00|3 days ago
I'd believe it was a joke if was a one-liner but this has far more detail then that.
this issue was more of a joke (am I allowed to do that?)
Not really a fan of the qualification here to possibly scare people off from calling them out either.
To clear, I have no problem with them hiding the repo, I have no problem with them changing their mind after the blowback, but it's frustrating when they can't own these decisions and try to hide behind it being a "joke".
ds300|3 days ago
trust me this was never a serious proposal
unknown|3 days ago
[deleted]
benatkin|3 days ago
simonw correctly describes it as "not technically open source" - though OSI doesn't have the trademark, the term open source, capitalized or not, refers to the what the Open Source Definition codifies. There are other terms such as shared source, for this sort of stuff.
cwillu|3 days ago
Dwedit|3 days ago
plesiv|3 days ago
In addition to his great sense of humor, Steve is usually ahead of the curve in terms of trends. There's a lesson in this. LLMs have become incredible constraint solvers ("SAT-solvers for code"). Well-thought-out tests, types, specs, and docs are all incredibly valuable constraints. This has big implications - for example what happens to licenses when you can cheaply rewrite the codebase and therefore unencumber it.
Iolaum|3 days ago
anitil|4 days ago
crabmusket|3 days ago
I have a personal theory that "tragedy of the commons" has a very specific meaning, and beyond this meaning it just adds confusion. This isn't your fault - it's an overused phrase.
I'd try to examine the root of your discomfort. Why does it make you feel bad? Avoid thinking about "big ideas" like the commons or the public good.
cwillu|3 days ago
pona-a|4 days ago
The performative closing of public contributions citing the slop scare felt disingenuous from the start. You couldn't be bothered to implement _any_ mitigations that leave the community engaged with the project?
Writing a contributor karma bot, moving to a non-social or obscure git forge (most slop contributors are resume farming and GitHub is the only forge the HR cares about), newbie-unfriendly non-public workflows like git send-mail, or references from Discord... This isn't an AGI on the other side of the screen, planning the perfect strategy to infiltrate your project; it's a sub-script-kiddie trying to fill a portfolio with quick "contributions" doing the more annoying version of "fixing typos" in docs.
steveruizok|3 days ago
aichen_dev|3 days ago
[deleted]
sluongng|3 days ago
ddtaylor|3 days ago
alt187|3 days ago
unknown|3 days ago
[deleted]
verdverm|4 days ago
threatofrain|3 days ago
javier123454321|3 days ago
monster_truck|3 days ago