Do people genuinely not understand how stupid it makes them look when they copypaste ChatGPT output onto social media like this?
Based on his tweets, Josef seems like a guy incapable of coming up with his own original thoughts.
BambuStudio has been violating PrusaSlicer AGPL license since their fork
21–30 of 45 posts
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#22It looks like generated by "AI", so I recommend taka a dose of scepticism before reading.
The original post that this commenter objected to, which has now been replaced by Hacker News with a tweet from Josef Prusa with none of the same technical detail, is from one of the primary players in this whole debacle. Here's the original post: https://github.com/jarczakpawel/OrcaSlicer-bambulab/blob/mai...
jarczakpawel@ (on Github) reimplemented their network plugin and was targeted with over-inflated legal threats (like Section 1201 claims about circumventing access control, which it did not do) and forced to take down his implementation. What he did is provide an open implementation of their closed source network plugin based on their open-source, AGPLv3 Bambu Studio.
This was not some random "AI slop post". This was a (seemingly AI written, yes) summary from the creator at the center of the current debacle, who seems to be the best non-Bambu expert we have on Bambu's networking plugin.
Josef Prusa's tweet is not at all equivalent information. Prusa's tweet seems to be little more than some conspiratorial thoughts about Chinese law and Bambu being a Chinese company. Does that play in? Maybe, I have no idea one way or the other, but it says nothing about the AGPL violations or the technical details of how tightly integrated the plugin is with Bambu Studio.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#23Earlier quoted context omitted.
This is nonsense. AGPLv3 is GPLv3 with an added term that extends it to SaaS/network hosted software as well as software distributed in binary or source form. What are you suggesting the AGPL allows that GPL does not? AI-generated text is worth skepticism, but humans can be idiots and spout nonsense too.
> AI-generated text is worth skepticism, but humans can be idiots and spout nonsense too. Sure, but anyone posting chains of incredibly long LLM generated tweets can safely be ignored as an utter moron.
I understand that filter, I think, but unfortunately your filter is failing you here.
The original post was replaced by Hacker News, and was originally a long post on Github - https://github.com/jarczakpawel/OrcaSlicer-bambulab/blob/mai... - detailing how tightly integrated Bambu's networking plugin is with their "forked from the community, long standing AGPLv3" Bambu Studio. That Github post is from the creator at the center of the current debacle, who is probably the foremost expert on Bambu's networking plugin that exists outside of Bambu at the moment since he reimplemented it from scratch.
There were no long LLM generated tweets in the original post. I agree that Prusa's tweets seem like a weak and conspiratorial argument about Bambu being a Chinese company and so something. They seem like a distraction and it's a shame HN changed the original post. Surprising they can even do that.
The AGPLv3 violations here are pretty clear. Bambu's networking plugin is a tightly integrated closed-source carve out of AGPLv3 code they forked from the open-source community.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#24Earlier 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?
It is kooky that you think some conspiracy nonsense about Bambu being a Chinese company and so something from Josef Prusa, is better than a detailed (if AI-written) analysis of all the ways that Bambu's networking plugin is a tightly integrated component of the AGPLv3 Bambu Studio from the creator of the only reimplementation of that plugin that exists/existed who is the direct target of Bambu's recent legal threats.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#25Earlier quoted context omitted.
> AI-generated text is worth skepticism, but humans can be idiots and spout nonsense too. Sure, but anyone posting chains of incredibly long LLM generated tweets can safely be ignored as an utter moron.
I understand that filter, I think, but unfortunately your filter is failing you here. The original post was replaced by Hacker News, and was originally a long post on Github - https://github.com/jarczakpawel/OrcaSlicer-bambulab/blob/mai... - detailing how tightly integrated Bambu's networking plugin is with their "forked from the community, long standing AGPLv3" Bambu Studio. That Github post is from the creator at t…
The information contained within might be accurate, but the information clearly wasn’t important enough for the person posting it to actually bother communicating it like a normal human being.
That’s pretty telling!
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#26it is okay for agpl3 app to consume propietary library , not the opposite that derived code must be same viral license
This sounds like pro-Bambu wishful thinking rather than an informed opinion. On what basis do you believe proprietary plugins or libraries are allowed under any conditions by the AGPLv3? And if you want to counter that you didn't say "under any conditions", I agree, but that means we need to discuss the particulars of this case to decide whether it's allowed or not. Bambu took existing open-source, AGPL slicer softwa…
Nah you cannot force proprietary library that consumed by fork of viral licenced app to changed it license.
For example of this case is Apple Game Porting Toolkit which is fork of Crossover version of Wine GPL , Apple modified the code add dependency to their own implementation of DirectX's D3DMetal which is proprietary licensed library. So GPTK is composed with mixed GPL Wine app + propietary D3DMetal.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#27it is okay for agpl3 app to consume propietary library , not the opposite that derived code must be same viral license
If you want to distribute binaries or code based on the (A)GPLv3, or use them to serve content over the wire, you have to distribute the source code of the entire software project under the (A)GPLv3. If part of that software is proprietary and licensed in such a way that you can't or won't distribute its code under the (A)GPLv3 or a compatible license, then you can't use any of the (A)GPLv3 code at all. Now, there is…
From i read that not "plugin"/module problem but library problem , difference is a lot. It's okay to depend on propietary library but not ok for propietary "plugin"/module.
Apple also doing this for their fork of CrossOver's Wine GPL called Game Porting Toolkit, composed by Wine + propietary D3DMetal DirectX library
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#28Earlier quoted context omitted.
This is much better than the current slop post. Could it be swapped, please @dang?
The article linked here is a consequence of the actions taken against the repository linked by OP, not a more 'credible source'. The file linked in by OP, is the main argument by Pawel Jarczak why his fork does not violate any copyright laws (may it be written by/with help of AI or not).
I didn't say it was necessarily more credible, although I understand that was mentioned further up.
Personally I found the article (not the tweets) much more useful to understand the context of all this, as someone very out of the loop. Certianly more useful to me than a long list of very specific, in my option largely LLM output, points about a codebase I'm entirely unfamiliar with with claims that seem to need a legal team and court case to be meaningful. Slop is somewhat unfair and I'm happy to be disagreed with.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#29Earlier quoted context omitted.
The article linked here is a consequence of the actions taken against the repository linked by OP, not a more 'credible source'. The file linked in by OP, is the main argument by Pawel Jarczak why his fork does not violate any copyright laws (may it be written by/with help of AI or not).
I didn't say it was necessarily more credible, although I understand that was mentioned further up. Personally I found the article (not the tweets) much more useful to understand the context of all this, as someone very out of the loop. Certianly more useful to me than a long list of very specific, in my option largely LLM output, points about a codebase I'm entirely unfamiliar with with claims that seem to need a le…
Indeed. It’s not clear at all to me that this is a better or even equivalent post to the one I submitted.
Re: BambuStudio has been violating PrusaSlicer AGPL license since their fork
#30Earlier quoted context omitted.
If you want to distribute binaries or code based on the (A)GPLv3, or use them to serve content over the wire, you have to distribute the source code of the entire software project under the (A)GPLv3. If part of that software is proprietary and licensed in such a way that you can't or won't distribute its code under the (A)GPLv3 or a compatible license, then you can't use any of the (A)GPLv3 code at all. Now, there is…
From i read that not "plugin"/module problem but library problem , difference is a lot. It's okay to depend on propietary library but not ok for propietary "plugin"/module. Apple also doing this for their fork of CrossOver's Wine GPL called Game Porting Toolkit, composed by Wine + propietary D3DMetal DirectX library
are you referring to the exception for proprietary libraries that are part of the operating system? an exception that is needed because otherwise it would be impossible to build GPL software for non-free operating systems.
wine is under the LGPL which allows linking to any non-free libraries as long as those libraries are available in a form that allows relinking to a changed version of the application.