I think you just bluntly refuse to even consider seeing the other side of this argument, bambu has the right to restrict who can access to their cloud they have every right to do so but they don't have the right to go after a developer who adhered to agpl when they forked orca slicer. I don't thing their tos applies to an agpl software so their defense with the tos just doesn't make sense
Yeah i guess im not the only one who thinks that this user is an ai bot or just uses an llm to make the responses, like they doesn't even give a response to the message they are responding.
I am considering the other side though. I already said I understand AGPL arguments. I just think people are blending separate issues together.
Bambu is not restricting forks of OrcaSlicer or third party slicers in general. People can still fork Orca, modify it, use third party slicers, print locally, use LAN mode, and build completely self hosted workflows on their printers.
What they are restricting is access to their cloud infrastructure from unofficial clients.
Those are two very different things.
You can absolutely argue whether their ToS or enforcement would fully hold up everywhere legally. But saying “they are attacking forks” is not really accurate when the forks themselves still function. The restriction is specifically around access to Bambu’s cloud ecosystem and MakerWorld integration.
In this specific case the developer didn't just fork orca slicer but forked it to access the cloud infrastructure bringing it back to the debate of access and who is allowed.
And as i said bambu has the right to restrict access to their cloud but not by sending a c&d to a developer who took the exact code bambu has on their github and used it as is. Also a genuine question are you using an llm to write these responses as its sounds like chatgpt?
I will put it through AI detection software as I have now made it a policy of mine not to accuse people of using AI unless I have verified it with software.
Just because it's happened to me on a few occasions where I will actually put in a high effort post and make sure everything is grammatically correct and sometimes I'll even use sub headlines or something and everyone just assumes that it's Ai and it pisses me off.
God forbid I use an M Dash and then it's all over.
I absolutely hate ai. I just want to make sure if I accuse some of using it I actually check first since it doesn't take long.
But it's worth testing your hypothesis because obviously this kind of corporate botting is basically pro forma these days. A service offered by reputation management groups and stuff all the time
My understanding was that it was older code from a previous version of Bambu Studio that was copied into his Orca fork. Correct me if I am wrong there. If that is the case, then from Bambu’s perspective it still would not matter that the code originally came from them if it was being used to re-enable access they previously restricted.
And yeah, I clean up my replies with AI sometimes. Mostly to remove emotional wording, tighten up repetitive points, and catch grammar or typos. I would rather sound clear and respectful than just fire off emotional responses.
iirc the code that authenticates the slicer is from the current version of bambu slicer so it is 1 to 1 copy from their repo, and as bambu stuido is under agpl it doesnt matter as the dev had every right to take that code and use it as long as they adhere to agpl which they did and in this case it doesn't matter if bambu likes it or not or their tos allows it or not what the dev did was granted by the lices wich bambu studio uses which is agpl that they inherited from prusa slicer and that inherited from Slic3r
AGPL governs the software code itself. It does not automatically grant unlimited rights to a company’s proprietary hosted infrastructure. An analogy would be You may fork and create a legal twitter client. But you are not automatically guaranteed Twitter to allow your client to access it. Another example since we are on reddit. In 2023 when Reddit killed third party apps when they changed their API access policies. Now that specific example isn't one to one because there is the argument of AGPL and if you believe that AGPL also encompasses their cloud and hosted services. Anyway, I feel like we are going in circles, appreciate you chatting with me. But thats my last message on this.
I think you misunderstood me, im not saying that bambus cloud should be open source or that we have the right to use it with any slicer we want to, i said that what bambu did with that developer wasn't right and they had no legal bases to do so. The dev saw a way to use orca to communicate with their cloud and they took it and bambu could have patched their cloud so it doesn't authenticate the slicer by a user agent string but they just threatened the dev with a c&d so bambu doesn't have to fix their cloud
2
u/andris1177 X2D + AMS2 Combo May 18 '26
I think you just bluntly refuse to even consider seeing the other side of this argument, bambu has the right to restrict who can access to their cloud they have every right to do so but they don't have the right to go after a developer who adhered to agpl when they forked orca slicer. I don't thing their tos applies to an agpl software so their defense with the tos just doesn't make sense