> Someone reverse engineered the plug-in and put it into orca slicer and then claimed that the plugin should have been GPLed to begin with which I find dubious. I don't really see it being much different than downloading closed drivers on Ubuntu but I'm also not a open source lawyer.
The GPLv3 specifically was written to address a problem called "TiVo-ization", which is when a hardware vendor uses some trick (DRM, proprietary blobs, whatever) to prevent users from actually running modified versions of the software.
The AGPL, the license of this particular software, extends the GPLv3 with protections for users of network services:
> Simply put, the AGPLv3 is effectively the GPLv3, but with an additional licensing term that ensures that users who interact over a network with modified versions of the program can receive the source code for that program. In both licenses, sections four through six provide the terms that give users the right to receive the source code of a program.
https://www.fsf.org/bulletin/2021/fall/the-fundamentals-of-t...
And on TiVo-ization: https://en.wikipedia.org/wiki/Tivoization
The Linux and proprietary drivers situation is more complicated, but proprietary drivers on Linux are generally restricted to interfaces that Linux chooses to expose to them for that purpose. But the Linux kernel seems to take a narrower view of what constitutes a derivative work than was likely intended by the FSF in writing the GPL. Under a "traditional" reading of the GPL, those proprietary drivers are meant to be illegal. Whether some or all of the linking done by proprietary drivers in the Linux kernel is really allowed by the GPL or not is somewhat untested, I think.
Is that why Linux sticks with GPLv2 instead of GPLv3?
Correction is much harder than starting off on the right side.
Sure, a manufacturer that didn’t need to course correct yet doesn’t mean they won’t change their stance in the future, but the same is true for one that already course-corrected.
We see this with privacy eroding laws continually - legislators will “listen” and course correct if there’s pushback, only to reintroduce the bill in the next legislative session, repeatedly, until it gets passed.
I’d prefer the one that hasn’t yet signaled a desire to do something negative in the past to one that has, even if they walked it back later.
Someone who isn’t racist because they grew up in a progressive family just means they were lucky. They often have never been tested under pressure.
On the other hand, someone who grew up in a racist family and ends up not racist means their beliefs are battle tested. This is a real test of character — it also tells me how they process information.
What you’re describing is a third case where someone pretends to correct but has no intention to, which I do not think Bambu’s original act of opening of LAN access qualifies.
Now I think the other dimension here is that people are expecting Bambu to believe in open source. They might not actually, which is their own opinion to have, but that’s a different problem altogether. I believe in local access but not necessarily open sourcing of everything so from my PoV, Bambu’s stance is perfectly consistent.
From Bambu’s historical and continued actions, specifically including the orca slicer actions that this blog post was about, there is additional signal that LAN mode backpedaling was more likely an appeasement action than a shift in principles to embrace a more open ecosystem.
Doesn't it sounds weird to you? I mean, what the reason they have to blur the line? Are they just clueless? Or maybe they fight for some political reason, like an anti-corporate stance, and Bambu is just a convenient target for them?
I'm asking, what you think of them, because I can't understand you. Your take on the conflict is incompatible with behavior of the people opposing Bambu. Or rather it leaves no good explanations for their behavior. When I notice it, I start digging, because if the situation doesn't have a good explanation, it means I do not understand the situation. But you just accept your understanding, so you have some good explanation for people's behavior?
It is very dubious way to subvert GPL, even GPL2, not to mention [A]GPL3.
It was discussed many times that you cannot have close-sourced plugin for GPL host program, as loading plugin is linkage and it is covered by full GPL (only LGPL has linkage exclusion).
This is in no way equivalent. You can't sync filaments, you can't monitor printers in your slicer, you can't monitor prints from your phone. This is like going backwards at least 5 years.
I find this shallow take really annoying, as it tends to derail most discussions ("you have LAN mode, so what are you complaining about").
Plenty of situations would make me feel differently, but I'm fine with their restrictions in this case.