An ongoing 3D-printer AGPL violation

There's a special kind of irony in a 3D printer company violating the AGPL. These are machines that literally build things layer by layer, yet the people behind them seem allergic to the idea of building on the work of others without taking more than they give. The AGPL exists specifically to close the "SaaS loophole"—the idea that if you modify open source code and run it as a service, you still owe the community your changes. A 3D printer running AGPL firmware isn't a SaaS in the traditional sense, but the license applies regardless of whether your product is a web app or a box of stepper motors and heated nozzles. What makes this violation "ongoing" rather than a simple oversight is the frustrating part. The open source community has a long and painful history of companies using GPL-family code, getting caught, and then dragging their feet on remediation. The BusyBox litigation spree of the late 2000s, the various VMWare and Cisco battles—the pattern is depressingly consistent. Companies calculate the risk of legal action against the cost of compliance, and too often, they figure the risk is low. And they're usually right, because who has the resources to sue a printer company over firmware? The deeper issue here is enforcement fatigue. The AGPL is one of the strongest copyleft licenses in existence, but a license is only as good as its enforcement. The community can shout from the rooftops, write angry blog posts, and rack up Hacker News points, but until someone actually takes these violators to court—or at least threatens to—the calculus doesn't change. The LWN article (https://lwn.net/SubscriberLink/1089390/46116614cc74b814/) is doing important documentation work, but documentation without action is just a diary of grievances. There's also a hardware-specific angle worth unpacking. When code is baked into a physical product, the compliance conversation gets murkier. Is the vendor obligated to provide source to every customer? What about the supply chain—do distributors bear any responsibility? The AGPL's network clause adds another wrinkle: if the printer has any network connectivity, the "remote interaction" trigger could apply. It's a reminder that open source licenses were written for a software world, and we're still figuring out how they map onto the physical realm. But "it's complicated" isn't a legal defense, and it shouldn't be a moral one either. The HN thread (https://news.ycombinator.com/item?id=49452980) is likely full of the usual takes—some defending the vendor, some calling for a boycott, some asking why anyone buys closed firmware printers anyway. But the real takeaway is simpler: the open source ecosystem runs on reciprocity. When companies take without giving back, they're not just breaking a license—they're breaking the social contract that makes projects like this possible. And that's not a bug in the AGPL. It's a bug in the people who think they're above it.