Move tests to closed source repo

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.

This is not gonna end well.

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.

The SQLite comparison someone mentioned is spot-on. SQLite has kept TH3 (their 100% branch coverage test suite) proprietary for years as a monetization strategy, and nobody bats an eye.

Whether tldraw's issue was a joke or not, it highlights a real tension: open source maintainers are watching AI companies train on their code, tests, and documentation - the very artifacts that make software reliable - and then use it to generate competing implementations. Tests are arguably more valuable than the code itself because they encode the specification and edge cases.

I suspect we'll see more projects adopt a split model: open source the runtime, keep the validation suite proprietary. It's a natural response when your test suite becomes a training signal for competitors.

Maybe we just Jai Tan to provide some fresh test data.

Read the thread, 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.

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.

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.

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.

I wonder if TLDraw realizes that Ai can probably run the software and generate an even better test suite. Days to replicate +1?

What a strange joke that wasted the time of so many.