Is it "Defending Open Source" or "Cyberbullying a High Schooler"? — A Look at the Downfall of an Indie Developer with 140K Followers
Foreword:
On June 10, 2026, a controversy erupted in the open-source community. A well-known independent developer with 140,000 followers accused a high school student of "plagiarizing" his open-source project and publicly expressed his dissatisfaction.
The incident quickly escalated, with supporters flooding the latter's project comment section condemning the "plagiarism." But as details surfaced, things were far from a simple act of "defending open source."
This article has no intention of picking sides, but only attempts to answer three questions: Legally speaking, did Burrow infringe copyright? Behaviorally, who was actually bullying whom? And what deep-seated issues in the open-source community did this storm expose?
An Issue, a Post, and Two Unequal Opponents
The two protagonists:
The author of Mole: A KOL (Key Opinion Leader) in the tech space on X (formerly Twitter) with 140,000 followers. He developed a Mac cleaning tool called Mole. The command-line version (CLI) is open-sourced under the MIT license, and there is also a paid desktop version (Mole Mac).
The author of Burrow: A high school student. He independently wrote code under the MIT license to create a free tool called Burrow, which has a UI and features similar to Mole's desktop version, and published it on GitHub.
The trigger for the controversy was: Burrow used the wording "a free alternative to the paid Mole Mac" in its project description.
Upon discovering this, the author of Mole did two things:
- He opened an Issue in Burrow's GitHub repository, pointing out issues with the promotional wording and the similar UI.
- Almost simultaneously, he posted a link to this Issue on X, publicly calling it out and stating that it was "quite chilling." He mentioned wanting to close the source code.
It was this second action that fundamentally changed the nature of the incident.
Legally Speaking, Did Burrow Actually Infringe?
This is a question that must be clarified first. The answer is: On the core issue, no.
Mole's CLI version uses the MIT open-source license. This license explicitly grants anyone the right to freely use, copy, modify, merge, publish, distribute, sublicense, and even sell copies of the software.
Choosing the MIT license is choosing a legally binding contract. It means that while the author enjoys the propagation benefits brought by open source, they must also accept that anyone can build a functionally similar tool, including a free one, based on this code.
So, is the similarity of UI and interaction considered plagiarism?
This is the most hotly debated part. A concept needs to be introduced: copyright law protects specific "expressions" (like code, icons), but does not protect "ideas," "functions," and "methods of operation."
The UI layout and interaction logic of a software are categorized as "methods of operation" or "ideas" in most judicial practices. If the first person to design a "pull-to-refresh" mechanism could permanently monopolize this operation, the entire internet's innovation would stagnate.
Therefore, as long as Burrow's front-end code was written line by line (even if written by AI) and didn't directly copy Mole's images, icons, or CSS files, then even if it looks similar, legally it belongs to "a lawful independent implementation," not an infringement.
Here's an analogy that might help: No one can monopolize the color "green."
If someone invented "green" and then claimed that anyone using green in the future was plagiarizing, it would clearly be absurd. UI layouts and interaction logic are treated as "ideas" and "methods of operation" under the law and are not protected by copyright. Only specific code, icons, and images are protected "expressions."
The Only Line Burrow Crossed
In its promotional copy, Burrow used Mole's commercial brand name mole.fit and the phrase "free alternative." This touched the boundaries of trademark rights and unfair competition. Less than 12 hours after the Mole author raised the Issue, the Burrow author updated the README and removed the related expressions.
At this point, the sole flaw in legal compliance was resolved.
The Real Bullying: Using 140,000 Followers to Crusade Against a High Schooler
If the incident had been limited to communication within the Issue, it would have been just a normal, even encouraging, course correction within the community.
But that post on X changed everything.
An account with 140,000 followers publicly posting a link to a specific project, accompanied by heavily emotionally biased words like "quite chilling," effectively acts as a clear signal directing followers' attention and pressure.
The power disparity here is extreme:
- On one side is an industry KOL with 140,000 followers.
- On the other is an up-and-coming high school developer with a GitHub project that had barely 400 stars.
Following this, a massive amount of aggressive and accusatory comments rapidly appeared in Burrow's Issue section and related discussions. Regardless of the Mole author's subjective intent, his actions objectively steered an unevenly scaled internet hate campaign against a minor independent developer.
The Mole author stated in the post that he "might make the CLI version closed-source in the future." This sentence exposes the essence of the storm: it wasn't a pure defense of the open-source spirit, but rather a stress response when the free Burrow posed a potential threat to his paid desktop version.
This isn't incomprehensible, but wrapping "commercial anxiety" in "open-source morality," and resorting to asymmetrical public pressure for the latter, deviates from the track of normal commercial competition.
Whitewashing After the Fact: The Elegant "Rational Moderates"
What's most infuriating isn't just the cyberbullying itself, but the whitewashing performance put on by a group of tech experts afterward.
A representative figure is Xuanwo. He is a member of the Apache Software Foundation and a top expert in the open-source circle.
A top expert, in the face of naked cyberbullying, says absolutely nothing about "bullying the small," but instead talks extensively about how "both sides are great" and "worth learning from." He forcibly whitewashes a public shaming orchestrated by a 140K KOL into "healthy interaction in the open-source community."
This isn't stupidity; it's malice. He knows better than anyone where the law and right/wrong stand, yet he still chooses to use his professional authority to endorse the unethical behavior of an insider.
Small-Peasant Mentality Won't Make You Rich
This turmoil reflects a deep-seated cultural dilemma in the Chinese open-source community: Many practitioners work in the most cutting-edge tech industry, but their business ethics and concepts of competition still carry strong pre-modern colors.
To sum it up in one sentence: "Deep down, many independent developers still think like peasants."
This is not a derogatory remark, but a metaphor worth pondering. The logic of an old peasant goes like this:
- I worked hard to clear a piece of land (wrote code).
- I grew crops (made a product).
- I built a fence (chose the MIT license, but secretly hoped others "wouldn't take it too seriously").
- If someone next to my land uses my methods to grow the exact same crops and gives them away for free, then they are "dishonorable," "stealing my craft," and "smashing my rice bowl."
This set of logic is rooted in the "favors" and "rules of propriety" of an agrarian society, rather than the "contracts" and "competition" of a modern commercial society.
But the foundational rule of open source is a legal contract, not a charity of "tossing someone a crumb." When a developer clicks the "MIT" option, they are not setting up a private plot protected by village regulations, but releasing the code into a public domain governed by modern rule of law and market rules.
You can continuously innovate technically to build new moats; you can pursue excellence in service to win users' willingness to pay.
But you cannot, after enjoying the dividends of open-source distribution, try to use moral condemnation and fan-driven public pressure to build back the very fence you legally and voluntarily gave up.
What Kind of Open-Source Ecosystem Do We Really Need?
The biggest warning from this incident isn't that a certain project was "borrowed," but the terrible signal it sends to all subsequent innovators:
If you abide by open-source licenses and create a legal alternative, you might be torn to shreds by those with a larger voice under the guise of "chilling them" or being "immoral."
When "morality" becomes an attack weapon that can be invoked at will—without bearing any legal responsibility—its suppression of innovation will be far worse than code plagiarism.
We call for a more mature open-source environment:
- Leave the law to the law. If there is suspicion of infringement, please file a DMCA or a lawsuit.
- Leave business to business. If you fear competition, choose your open-source licenses carefully, or deeply cultivate irreplaceable technical barriers.
- Leave morality to morality. Using asymmetrical public opinion power against an individual with no actual illegal behavior is inherently immoral.
The essence of open source is openness and collaboration based on contracts, not charity and dependence based on personal favors. Only when more people learn to respect contracts and face competition head-on can China's open-source soil truly modernize.
Don't let the rustic plain morality become the final straw that crushes the next generation of innovators.
Thank you all for your support! If you found this interesting, please don't hesitate to like, watch, and share!
To see my articles as soon as they drop, don't forget to star ⭐, so you won't lose track of us later.
That's all for today.
Top comments (0)