BambuStudio has been violating PrusaSlicer AGPL license since their fork
1–10 of 45 posts
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#2It looks like generated by "AI", so I recommend taka a dose of scepticism before reading.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#3This interpretation would mean that you could not produce AGPL licensed code which loads some code in dynamically. Like say you couldn't have an AGPL licensed web-browser which sometimes loads pages whose JavaScript's source-code is obscured. ?
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#4It looks like generated by "AI", so I recommend taka a dose of scepticism before reading.
A more credible source from Prusa (the company behind the source slicer that bambulab forked)
https://www.tomshardware.com/3d-printing/josef-prusa-warns-c...
The situation is interesting and kind of a grey area. The way they structured the network code as a plugin that downloads after first run is obviously to avoid violating the AGPL license, but if you don’t install it, large parts of the slicer are inaccessible. So it’s not at all like a normal plugin.
Edit: a more direct source. https://x.com/josefprusa/status/2054602354851254330
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#5This interpretation would mean that you could not produce AGPL licensed code which loads some code in dynamically. Like say you couldn't have an AGPL licensed web-browser which sometimes loads pages whose JavaScript's source-code is obscured. ?
IIRC the difference is the effective requirement of having it for the intended function of the software; To whit: Printing to a Bambu printer. It's a legal gray area but the general legal consensus as I understand it is that the dynamic loading is enough most of the time up to the point where it's a requirement for functionality.
Of course, IANAL and just a random passerby with a SUPER rough understanding.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#6It looks like generated by "AI", so I recommend taka a dose of scepticism before reading.
A more credible source from Prusa (the company behind the source slicer that bambulab forked) https://www.tomshardware.com/3d-printing/josef-prusa-warns-c... The situation is interesting and kind of a grey area. The way they structured the network code as a plugin that downloads after first run is obviously to avoid violating the AGPL license, but if you don’t install it, large parts of the slicer are inaccessible. S…
This is much better than the current slop post. Could it be swapped, please @dang?
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#7This interpretation would mean that you could not produce AGPL licensed code which loads some code in dynamically. Like say you couldn't have an AGPL licensed web-browser which sometimes loads pages whose JavaScript's source-code is obscured. ?
AFAIK, the code of the network "plugin" is dynamically loaded, but the version string is hardcoded in Bambu Studio. The analogy is not exactly right IMO; the browser is not restricted to a specific website or a specific version of that site.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#8This interpretation would mean that you could not produce AGPL licensed code which loads some code in dynamically. Like say you couldn't have an AGPL licensed web-browser which sometimes loads pages whose JavaScript's source-code is obscured. ?
The networking code is not some 3rd party content that happens to be loaded. It’s an integral part of bambu studio, and if you don’t install it, large parts of the apps functionality won’t work.
By a common sense view it is not a plugin at all, it’s part of the app that they have structured in a weird way to try to avoid the obvious license violation.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#9This interpretation would mean that you could not produce AGPL licensed code which loads some code in dynamically. Like say you couldn't have an AGPL licensed web-browser which sometimes loads pages whose JavaScript's source-code is obscured. ?
Software licensing disputes have almost nothing to do with the technical mechanism that loads the code into RAM. The court will look at the totality of the facts: what is the product, how is it normally operated, who is selling it. There's a lot more common sense involved than programmers like to think (but it's not completely about common sense).
For example the Nvidia driver gets to ignore the Linux kernel license because even though it links with the kernel, when considered as a complete package it's not a derivative work of the kernel. It is its own product that can be plugged into various kernels such as Windows and Linux, and the small adapter layer for each kernel doesn't change that.
Some German court even once interpreted GPLv2 to prohibit tivoization.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#10Earlier quoted context omitted.
A more credible source from Prusa (the company behind the source slicer that bambulab forked) https://www.tomshardware.com/3d-printing/josef-prusa-warns-c... The situation is interesting and kind of a grey area. The way they structured the network code as a plugin that downloads after first run is obviously to avoid violating the AGPL license, but if you don’t install it, large parts of the slicer are inaccessible. S…
This is much better than the current slop post. Could it be swapped, please @dang?
@dang doesn't do anything. email hn@ycombinator.com to get his/other moderators attention (which I did).