Claude.md
🥀🥀🥀
This is a most excellent place for technology news and articles.
Where fork?
Thank you. Forked.
In case someone comes across this and doesn't know, "forking" a repo by just clicking that button on github won't preserve your copy if the upstream repo gets taken down. If you're trying to preserve it, make sure you have a copy independent of github's control. Like a local backup
Excellent point, thank you.

I'm happy with my slightly modded Ender 3 Pro, but if I ever upgrade the Snapmaker U1 looks nice. I'll only buy from a company that supports open source firmware. Bambu is trash, unfortunately every 3D printing related YouTuber seems to have happily taken a sponsorship from them so they are everywhere now. I hate it.
The problem with Bambu is they are not trash at all. Their printers are high-quality, and the way they integrate with their proprietary slicer (that they totally stole from the community before locking it down) and MakerWorld is genuinely excellent.
I have 3 Bambu printers. I don't buy their products anymore (my newest printer is an SV-08 max), but I still use the ones I have and they're excellent, easy machines. And if someone new comes to me wanting a starter "just click print and it works" solution, I'm still likely to point them towards an A1 mini. They're cheap and work great out of the box with zero handholding from me required.
And that's why I kinda hate them. They don't have to be dickheads, but choose to be. Their products are fantastic, and I'd honestly be using Bambu Studio for them instead of Orca anyway.
their proprietary slicer
That's the problem, it cannot be proprietary when based off slic3R. It's not their property to lock down.
The slicer is not proprietary, but the networking plugin for printer communication is
I don't know how their plugin work, but wouldn't AGPL "unproprietary" it?
Jarczak’s fork crossed the line by injecting falsified identity metadata into its network communication. “In simple terms: it pretended to be the official Bambu Studio client when communicating with our servers.”
If it's easy enough to get access to your cloud infrastructure by just changing some metadata about the connection, then you really should re-think your authentication systems. If I were to publish the exact model and pinning of the lock on my house, it would be silly of me to be mad that someone used that to make their own keys.
The DMCA is literally written in a way that they could write “DO NOT USE” in a text file and include it with firmware and claim that using the firmware Ina way they didn’t like was “breaking a digital lock”
Honestly I’m perfectly fine with the DMCA just being entirely revoked at this point. It has enabled more bad than it has done good, even when things went “right”
what good has DMCA done???
Great move by Snapmaker. In considering buying a new printer soon I am very annoyed by how difficult it is to know beforehand how much functionality of a printer is locked behind cloud connectivity that can be remotely disabled at any point. I know Bambu is to avoid absolutely thanks to the very public backlash they got but what about the others?
I know Prusa is a shining example of letting their customers own their devices but they are pricy. I didn't know Snapmaker had the same kind of mentality until now thanks to that move.
It looks like Rossman is saying that anyone can post this code because it's an open source, GPL code. Rossman also posted the code: https://www.youtube.com/watch?v=1jhRqgHxEP8&t=2s
Right, there are many forks of the software, which is allowed under the AGPL licence.
Slic3r by Alessandro Ranellucci established the original open-source foundation.
Then PrusaSlicer forked from that -ok.
Then Orcaslicer forked from that -ok.
Then Bambu locked down it's fork - not ok, violation of the slic3r AGPL.
It's like..can I borrow your car? puts a bumper sticker on it, changes the locks, my car now.
Slic3r is licensed under the GNU Affero General Public License, version 3.
The GNU Affero General Public License (AGPL) is a strong copyleft, free software license designed to ensure source code remains open, even when software is run over a network. Based on GPLv3, it closes the "ASP loophole" by requiring companies that modify and offer software as a service (SaaS) to make the source code available to users.