Live data from Hacker News

An ongoing 3D-printer AGPL violation

lwn.net

91–100 of 247 posts

Re: An ongoing 3D-printer AGPL violation

#91

For current owners who want to avoid Bambu's servers entirely, consider LAN mode with OrcaSlicer and this open source reverse engineered networking plugin: https://github.com/ClusterM/open-bamboo-networking I have verified that my P2S in LAN mode never attempts to make external connections at all (blocked it anyway, of course) and OrcaSlicer + this plugin never attempts to connect to any of Bambu's servers. My P2S is…

Is it possible to back out the firmware updates and setup that came along with this change to get self sufficient, or is that not necessary? I recall hearing that a firmware update made the printer (P1S in my case) phone home even potentially when in LAN mode. This is an area where I just kind of gave up and let it happen, though I kind of regret it now.

Re: An ongoing 3D-printer AGPL violation

#92

Earlier quoted context omitted.

You want them to go after the buyers ??

Yes. It's the only way to cause material harm to the company.

Not at all, do you not understand how customs works? What cause of action do you propose against the buyers? Do you not care about the law, you just want maximum retribution?

Re: An ongoing 3D-printer AGPL violation

#93
post #59

> A 3D-printing user from Poland, Paweł Jarczak, reverse-engineered the User-Agent string and network code, which resulted in a DMCA takedown notice from Bambu Lab. "GitHub, of course, honored it, because Microsoft." Which is somewhat funny because a lot of high-impact piracy stuff is on Github and has been for years. GenP (Adobe) and Massgrave MAS (anything Microsoft) come to my mind.

> GenP (Adobe) and Massgrave MAS (anything Microsoft) It's questionable whether those two companies care that much about piracy, they make most of their money off enterprise, right? For a while I heard it theorized that Adobe and Microsoft largely let people get away with it, since it still keeps them in the ecosystem and therefore makes them likelier to use those products at work. Versus Bambu which probably still s…

> I heard it theorized that … Microsoft largely let people get away with it, since it still keeps them in the ecosystem

That is more than just a theory, their own documents (I can't remember if they were leaked or officially released as part of the big anti-trust case) stated that this was essentially their policy for poor eastern counties: if they wouldn't be paying for it anyway MS preferred them to use it rather than something else (like Linux, or something locally created, etc,).

It was less openly ignored in the case of students, or people using work licenses (or just pirate copies) at home, but the above and the lack of enforcement would indicate it was ignored for that reason.

Re: An ongoing 3D-printer AGPL violation

#94
post #32

Earlier quoted context omitted.

Generally, when you ask people who have any understanding of law, they respond, well, of course not. No one with any sanity at all would try and test the GPL in court. They know what's going to hold up. I do believe that the GPL will eventually be broken. However, it won't be broken in ways such as happening now. It'll be broken when some company is able to show the court that they were doing a lot of things to ensur…

You're talking about the GPL though, OP was talking the AGPL

For this discussion it makes no difference.

Re: An ongoing 3D-printer AGPL violation

#97
post #44

Earlier quoted context omitted.

Banning import/sale of the product into the US is worth a hell of a lot.

I wouldn't call that a win, though. I have a Bambu printer and it's very difficult to reproduce their tuning on open-source hardware or software. I think Klipper has vibration compensation now, but pressure advance and some other things require some tinkering and waste in order to set correctly, and you have to re-do them on any new nozzle/filament/temperature. Deciding nobody can have the software at all is complete…

> Deciding nobody can have the software at all is completely opposite to the spirit of the license.

Any import block would be on the hardware, not the software. And the software would need to be released for other territories anyway.

Re: An ongoing 3D-printer AGPL violation

#98
post #48

Earlier quoted context omitted.

Some people like to use tools to make something possible/easy. Others like the tools themselves. The Bambu printers, at the time of their release, were an incredibly superior pieces of hardware and software that was priced very very well and, this was a really big deal , worked fully right out of the box. It was a pretty clear choice in either dicking around with the tools, or actually using the tool to make things .…

Prusa's printers also worked out of the box. They cost slightly more, and their staff aren't volunteers.

No they did not. Calibrating flow and pressure advance was entirely manual. Vibration compensation/input shaping did not exist until 2023 [1], and was also entirely manual. The Pursa XL (only thing remotely comparable) was over double the price [2], with the Core One (Bambu competitor) not coming out until 2024 [2]. Their MMU was a clusterfuck of tinkering [4], so when Bambu released the AMS, people were trying to figure out ways to get it to work on the Prusa! Even now, the new Prusa MMU alone is almost as much as a Bambu + AMS!.

Bambu shook the industry because it was better in all ways that mattered if you actually wanted to make something.

[1] https://www.fabbaloo.com/news/prusa-research-unveils-mk4-inp...

[2] https://www.3docity.com.au/blogs/3dprinting/corexy-printers-...

[3] https://toms3d.org/2025/02/11/finally-prusa-takes-on-bambu-c...

[4] https://www.reddit.com/r/prusa3d/comments/x3m76q/did_you_reg...

Re: An ongoing 3D-printer AGPL violation

#99
It's an open mqtt server if you have creds..... 300 lines of python made by claude totally power mine over a raspberry pi zero.... yes, it sucks they stole, but their hardware is fantastic and if good artist's copy, great artist's steal.

Re: An ongoing 3D-printer AGPL violation

#100
post #94

Earlier quoted context omitted.

For this discussion it makes no difference.

It very much does, as this is a AGPL violation being discussed, not a GPL violation.

By "it doesn't make a difference" they meant that the argument applies equally for both, and if it fails for one it fails for both.
Post reply on HN