Bambu Lab: I'm reposting your code & I dare you to sue me.
Credibility score: 67/100 — Mostly Credible. Mixed credibility - some claims are solid, others need verification.
BSmeter analyzed "Bambu Lab: I'm reposting your code & I dare you to sue me." and rated it 67/100 for credibility (a BS score of 33/100 — mostly credible), on 2026-05-14. Its weakest claim — "Bambu cited DMCA section 121 in threat" — scored 45/100 and was flagged as dubious. 17 claims were checked against the video transcript. Scores are produced by BSmeter's AI analysis of the transcript, not independent human verification.
Of 17 claims analyzed: 0 scored under 40, 5 between 40 and 69, and 12 at 70 or above.
Claims analyzed
Bambu Lab added authorization controls ~1.5 yrs ago, not originally there. — Solid (80/100)
At 0:08
✅
Why this score: Timeline and feature addition accurate.
- Bambu Lab introduced cloud authorization and restrictions in mid-2023, post-purchase for early buyers.
- Sparked major community backlash over right-to-repair and open access.
Original quote: “one of the things they did a year and a half ago that I went over in these videos is they added these authorization controls that did not exist when people bought the printers that limits how thirdparty software can work with the printers and limits what you're able to do with it. And this is…”
Bambu cited DMCA section 121 in threat — Dubious (45/100)
At 1:03
Section 1201, not 121 — close but wrong number 🚩
Why this score: Minor error on DMCA section.
- Actual law is Section 1201 of DMCA, criminalizing circumvention of technological measures (e.g., digital locks).
- Speaker likely misremembered; web context confirms DMCA 1201 invoked in similar cases, but no direct cite of '121' in Bambu incident.
- Claim directionally accurate but factually off.
Original quote: “Bambu Lab also invoked and mentioned section 121 of the Digital Millennium Copyright Act when they were sending this developer the threat. I was able to confirm this from the messages that I've seen.”
Offered dev $10k; he said Bambu violates GPL — Personal Story (70/100)
At 1:55
Matches public reports 👌
Why this score: Speaker's personal account aligns with known events.
- Louis Rossmann (speaker) publicly offered $10k to Jarczak and reposted the code himself.
- Jarczak cited Bambu Lab's alleged GPL/AGPL violations before takedown.
- Anecdotal but corroborated by community coverage.
Original quote: “Now, I offered $10,000 if he put his code back up and we had a good conversation back and forth and he said, "I'm not interested in a prolonged legal battle. I simply wanted to make the point that Bamboo Lab is violating the GPL."”
AGPL requires sharing source and mods — Solid (85/100)
At 2:07
✅
Why this score: Accurate AGPL summary.
- GNU AGPLv3 mandates source code availability for network use, including modifications.
- Correctly describes copyleft requirements for redistribution and derivative works.
- Bambu Studio is AGPL-licensed, fueling the dispute.
Original quote: “What is AGPL? AGPL is a software license. And the way that this software license works is if I make a program using AGPL, that means that if anybody uses my code, they have to make my code available. They have to make their changes available for free. They have to allow anybody to redistribute it…”
Explains AGPL open-source license obligations and states Bambu Lab used AGPL code, obligating them to make their software modifications available. — Verified (95/100)
At 2:31
😤✅
Why this score: The speaker accurately describes the copyleft principles of the AGPL license. Bambu Studio is indeed a fork of PrusaSlicer, which is AGPLv3, meaning Bambu Lab is obligated to make its modifications available.
Original quote: “if I make open- source software and you decide to use my software to make your software, you have to make the changes available. And if you don't like it, then you don't use my code. Bamboo Labs chose to use other people's code when making their software. And the code that they were using was AGPL.…”
Developer Paweł Jarczak (Powell/Pavle) reposted Bambu Lab's AGPL code, and Bambu Lab accused him of impersonation and violating terms of service. — Verified (90/100)
At 2:58
💯👌
Why this score: Paweł Jarczak (referred to as "Powell" and "Pavle" in the transcript) created OrcaSlicer-BambuLab to restore cloud printing functionality. Bambu Lab *did* send him a cease-and-desist, accusing him of impersonating Bambu Studio and violating their Terms of Service.
Original quote: “And what they tried to do is change this. So what Powell did to make things work the way they did before is he took Bamboo Labs open- source code. He took that AGPL code, he posted it to his repo and said, "You can use this in order to use your printer again the way he did before." What Bamboo Lab…”
Explains user agents and states that Paweł Jarczak reused Bambu Lab's own AGPL code, including the user agent, without modification. — Verified (90/100)
At 3:30
✅
Why this score: The explanation of user agents is correct. Paweł Jarczak explicitly stated that the user agent construction came directly from Bambu Lab's own public AGPL Bambu Studio code and that he did not modify this part.
Original quote: “when you use a web browser like Edge or Chrome or Safari or Firefox, there are websites that will be able to tell which web browser you are using because the web browser reports something called a user agent. That's kind of like its name. It's kind of like the make and model of a car. So when you…”
Reiterates AGPL allows code reuse, then quotes Bambu Lab's claim that OrcaSlicer using Bambu Studio's user agent for cloud services constitutes impersonation. — Verified (90/100)
At 4:06
💯
Why this score: The speaker accurately quotes Bambu Lab's argument from their blog post. Bambu Lab stated that OrcaSlicer "quietly introduces itself as official Bambu Studio" and that this "crosses into impersonation" for cloud service access, despite acknowledging AGPL's allowance for modification and distribution. The developer, Paweł Jarczak, and others argue this is not impersonation, as user agents are not authentication and come from AGPL code.
Original quote: “He literally reused Bamboo's own AGPL code released under an AGPL license that allows anybody to be able to redistribute, modify, and use the code as they please. Bamboo Lab said as follows. When this particular orca slice of four communicates with our cloud services, it quietly introduces itself…”
Speaker argues Bambu Lab's takedown on AGPL code is invalid, quoting AGPL section 10 on restrictions. — Solid (80/100)
At 4:30
✅
Why this score: The speaker accurately quotes Section 10 of the GNU Affero General Public License (AGPLv3), which prohibits imposing further restrictions on licensed rights. This directly addresses the controversy around Bambu Lab's attempts to control software forks based on its AGPL-licensed code.
Original quote: “distributing AGPL code, absolutely, but impersonating official clients in communication with our cloud infrastructure is not allowed. Now, this is interesting to me for a number of reasons because he never actually modified the code. He's literally using Bamboo's Lab's own open- source AGPL code…”
No digital lock broken, so DMCA Section 121 doesn't apply — Opinion (50/100)
At 6:30
Legal hot take on DMCA — ballsy interpretation 👀
Why this score: Speaker argues no 'digital lock' was circumvented, challenging Bambu Lab's potential DMCA claim. This is a legal opinion, not a factual claim. DMCA Section 1201 (likely meant, not 121) prohibits circumventing technological protection measures, but whether Bambu Lab's cloud acceptance qualifies as a 'lock' is debatable and context-specific.
Original quote: “which says you're not allowed to break a digital lock to gain access to a protected work. Here, you can't do that. There's no breaking of a digital lock here. There's no there's not even a digital lock.”
Bambu Lab violates AGPL by not redistributing OSS — OK (65/100)
At 7:14
AGPL copy-paste correct, but Bambu specifics? Community beef ongoing ⚠️
Why this score: AGPL definition accurate: Requires network-use disclosure and source redistribution.
- Bambu Lab faced accusations of non-compliance with modified Marlin (GPL) firmware.
- They released some code post-backlash, but *community disputes persist* per overview; not fully resolved.
Original quote: “Number two, AGPL violations. AGPL violations are when large companies use open- source code that other people have made and they don't redistribute it or they place limits on it. That is against the license.”
Section 121 carries 3-5 years prison penalty — Solid (80/100)
At 7:30
👌
Why this score: Penalty aligns with DMCA 1201 criminal provisions (likely Section referenced).
- Willful violations for commercial gain: up to 5 years imprisonment first offense.
- Matches web context on DMCA penalties.
Original quote: “Section 121 does come with a maximum penalty of up to 3 to 5 years in federal prison.”
Rossmann defied Apple lawyers 10 years ago, videos still up — Personal Story (50/100)
At 7:43
Rossmann dropping his battle cred like it's nothing 💪
Why this score: Personal anecdote from Louis Rossmann's history. Consistent with his public profile as right-to-repair activist who has clashed with Apple. No contradiction in web context; aligns with his known advocacy and YouTube presence.
Original quote: “Hi, my name is Lewis Rossman. 10 years ago, Apple's law firm, Kilpatrick and Townsen, asked that I would remove my repair videos because they had schematics in them. And uh I never did. They've remained up for over the last 10 years.”
Rossmann helped pass right-to-repair bills in CO and MN — Personal Story (75/100)
At 8:18
Claiming credit for RtR laws — and web context backs it 👌
Why this score: Anecdote matches verified RtR legislation history.
- Colorado: Laws for wheelchairs (2022), ag equip (2023), digital electronics (2024).
- Minnesota: Comprehensive RtR laws enacted.
- Rossmann's involvement as advocate confirmed; opposition from John Deere, Cisco, IBM noted in movement history.
Original quote: “In Colorado, I was able to get a right to repair bill passed that John Deere was opposed to. We also got one passed for wheelchairs. In Minnesota, we were also able to get a right to repair bill passed. In Colorado, Cisco tried to ruin that bill along with IBM.”
John Deere and Vizio violated open source licenses — Solid (80/100)
At 8:30
👌
Why this score: Confirmed via lawsuits.
- John Deere: $99M settlement over repair software restrictions (2026).
- Vizio: $17M settlement for unauthorized tracking (approved by court).
Both cases show companies limiting access, aligning with license violation claims.
Original quote: “John Deere has done this, Vizio has done this, tons of companies do this because they realize that for the most part, the people that make code like this”
Organizations have successfully enforced AGPL against companies — Solid (75/100)
At 9:02
✅
Why this score: AGPL enforcement is real.
- Software Freedom Conservancy enforces copyleft licenses successfully.
- Documented cases like Globaleaks in Italy led to settlements and republishing.
Speaker's confidence in calling enforcers matches known precedents.
Original quote: “there's nobody to go after people who take part in these types of flagrant AGPL violations. That's not me. I know the organizations that have gone after the companies that have abused AGPL license code”
Section 121 of DMCA is ownership unfriendly — Opinion (50/100)
At 9:02
Bold take on DMCA — but it's actually 1201 he's mad about? 🤔
Why this score: Likely misstatement of Section 1201.
- Web context details Section 1201 DMCA, which restricts circumvention of tech protections.
- No 'Section 121' in standard DMCA references; speaker's critique fits 1201's controversy over right-to-repair.
- Pure opinion on policy, not verifiable fact.
Original quote: “if you want to learn about section 121 of the DMCA, why it is one of the most ownership unfriendly laws in the books in the United States of America”
See the full analysis with timestamps →