| ▲ | cherioo 4 hours ago | |
Before: user can print via cloud or locally with custom slicer at the same time easier. Some time in 2025: firmware updates make user choose between cloud XOR locally. Enabling local mode allows using custom slicer, but disables cloud printing or monitoring. Folks were up in arms because they wanted both, and openness. Latest fork: a specific new custom slicer impersonates UA to submit print via bambu cloud, so it gives the pre-2025 experience. Bambu sues this new fork. Actual OrcaSlicer working locally is fine. | ||
| ▲ | dangus 4 hours ago | parent [-] | |
Bambu didn’t sue, they sent a cease and desist letter. Just to be pedantic. I don’t know what the fuss is about. This whole issue has nothing to do with the open source ecosystem. It has everything to do with the part where Bambu does not authorize 3rd party programs to contact their cloud servers. I totally agree that Bambu has their head up their ass here, but still, it’s not an issue that would make me want to choose another inferior or more difficult to use printer at this time. I own a Bambu printer precisely because it’s the iPhone of printers. It’s a tradeoff. If it ever enshittifies to the point of becoming a paperweight I’m personally not that worried about it. I paid under $300 multiple years ago for this printer. I know that’s not nothing and I don’t want to be wasteful but it’s not something I’ll be particularly upset about. It’ll be Bambu’s loss when I don’t buy their next products or when I stop buying their replacement parts and filament. | ||