#HobbyStreak day 1341:

More #3Dprinter shenanigans.

Got a good print, and then another. Still haven't gotten #OrcaSlicer gcode from linux to run.

#3Dprinting #Elegoo #CentauriCarbon2

#HobbyStreak day 1340:

Ya boi Erik hath ruined his #3Dprinter already. Printing didn't go as planned, lots of pubic hair and at some point (lunch called, the print came loose AGAIN and clogged the nozzle which then broke).

The 0.2 nozzle is now deaded, so I reinstalled the 0.4 and worked with gentler settings and raft.

Still haven't gotten the printer to recognise gcode by #OrcaSlicer on linux. Only Windows based. Suggestions welcome.

#3Dprinting #Elegoo

The Flashforge AD5X: Why I’m Done With Their Walled Garden

1,110 words, 6 minutes read time.

I wish I had known that the Flashforge AD5X was an afterthought—a machine clearly built with cost-cutting as the primary driver rather than user experience.

I was actually looking at QIDI printers when I stumbled upon the AD5X, a decision I now regret.

Don’t get me wrong; I appreciate the machine for what it is because I realize the price point dictates certain trade-offs. It feds my maker mentality, and I was willing to work within its limitations.

However, the recent “walled garden” attempts, implemented well after the sale, have completely soured my opinion of Flashforge.

Had I realized the company was planning to force this closed ecosystem on its users, I would have moved on; in fact, avoiding that exact dynamic is precisely why I didn’t choose a Bambu printer in the first place. From the underwhelming, sluggish touchscreen to the persistent technical flaws that have fueled thousands of online complaints, it is far from the well-engineered tool it was marketed to be. I have reached a point where my needs and the manufacturer’s roadmap are fundamentally incompatible, leading me to make a clean break from their ecosystem.

The Firmware Lockdown

My decision to stay frozen on Firmware 3.0.9 is a calculated move to preserve the utility of my equipment. This version is the last to offer a degree of functional independence before the manufacturer began implementing restrictive lockdown measures. By staying on this specific release, I avoid the firmware updates that effectively block direct local printing.

These updates have transformed the AD5X from a standalone tool into a cloud-dependent terminal. By mandating that the printer be online and tethered through their proprietary servers, the company has prioritized their own oversight over the user’s ability to operate their machine independently.

I should be free to print whatever I choose without their inspection or approval. I bought the machine — it should remain my machine.

I believe we have the right to be secure in our persons, houses, papers, and effects, and I certainly do not need tech overlords deciding what I can and cannot do with the equipment I own.

The Linux & Orca Slicer Workflow

My operational requirements are specific: I run Linux and rely on the stock version of Orca Slicer for its stability and feature set. Unfortunately, this ecosystem is not supported by the manufacturer, who seems intent on forcing users into their own proprietary software stack. Rather than hoping for future support or accepting a broken configuration, I have chosen to take control of my own technical variables.

I have implemented the necessary workarounds to isolate the machine from update servers, ensuring that the tool I rely on remains consistent. This is not a “fix” for a broken device, but a proactive choice to prioritize my technical requirements over the convenience of a forced, proprietary cloud environment. My workflow stays mine, and I refuse to ask for permission to use the tools I rely on.

Exploring Open Alternatives

As I look at where I go from here, I am exploring more open alternatives, such as the ZMod project, which aligns with my need for deeper control and hardware transparency. Projects like these represent the polar opposite of the current manufacturer trend, offering a path where the user remains the primary stakeholder in their own hardware.

The current industry trajectory feels increasingly like the “HP Ink” model, where the printer is a locked-down device designed to restrict consumer choice in materials and software. This “walled garden” approach treats highly capable, technical machines like disposable office appliances. I am moving away from this dynamic in favor of systems that respect my autonomy as a creator.

Conclusion

The divergence between the maker community and these proprietary ecosystems has reached a breaking point. Tethering hardware to cloud-only platforms forces users to choose between subservience to a manufacturer’s roadmap or the path of the tinkerer. Having worked in tech and internet technologies for over thirty years now—where did the time go?—I know that communication should be a simple matter of a computer sending a signal via wire or Wi-Fi to a printer. Whether referred to by number or by descriptive protocols like SSH, HTTP, or HTTPS, these ports are fundamental technology that has existed for decades. What is happening here is that the software port on the printer is being intentionally blocked, forcing the device to contact Flashforge servers to receive an “approved” and “sanitized” file.

By choosing to step outside of this managed ecosystem, I have opted for a direction where my tools remain under my control, serving my needs without the interference of forced updates or remote service requirements. This will be the last Flashforge product I own, and once this machine reaches the end of its life, I am done with them unless they fundamentally change their stance. Time will tell. The future of my workshop lies in open, transparent systems where ownership is not merely a legal status, but a functional reality.

Take Action: Reclaim Your Hardware

1. Secure Your Own Perimeter (The “Gateway Cutoff”)

If you haven’t been locked out yet, take control of your network settings immediately to prevent your printer from “phoning home”:

• Assign a Static IP to your printer.
• Clear the Gateway and DNS fields (or set them to a non-functional address like 192.168.0.0).
• Verify: This ensures your machine remains a local tool, immune to forced cloud-based “updates” that remove your autonomy.

2. Join the Fight for Right to Repair

As advocates like Louis Rossmann have shown, the battle for ownership isn’t just happening in our workshops—it’s happening in our legislatures. If you are tired of companies treating your property like a leased appliance, don’t stay silent:

• Find Your Representative: Use House.gov to identify and contact your local representative.
• Be Clear and Direct: When you call or write, mention specific legislation (like the REPAIR Act). Tell them you are a constituent who believes that if you bought it, you own it—and that includes the right to repair, modify, and use your equipment without manufacturer interference.
• Follow the Leaders: Support organizations and advocates like the Repair Association and Louis Rossmann who are actively fighting to dismantle the anti-consumer “parts pairing” and software-lockdown models that plague our industry.

D. Bryan King

Sources

• Comprehensive Response to Bambu’s AGPLv3 Violations – Software Freedom Conservancy
• Bambu Lab Faces Open Source Licence Firestorm Over OrcaSlicer Fork
• Drama at Flash forge! EULA includes spying on what you print.
• Migliaccio & Rathod LLP: Consumer Protection and Class Action Investigations
• MakerWorld launches Creator Copyright Protection Program – VoxelMatters
• Selling 3D Printed Items – A Legal Guide | All3DP Pro
• What Is RFID Filament? The Guide to Smart Spools – Snapmaker
• Is RFID Filament Killing Open 3D Printing? – YouTube
• Take a Stand for Maker Rights and the Future of Additive Manufacturing
• The differences between open-source printers and closed-source printers
• GNU Affero General Public License, Version 3
• Electronic Frontier Foundation: Right to Repair
• The Repair Association: Right to Repair
• FTC Policy Statement on Repair Restrictions
• Rossmann Repair Group
• SFC Baltobu GitHub Repository
• U.S. Copyright Office Guidance on AI and Copyright
• Bambu Lab Accused of AGPL Violations
• The Future of Open Source 3D Printing – 2026 Analysis
• Software Freedom Conservancy Takes on Bambu Lab
• The Right to Repair is Coming to 3D Printers
• RepRap Wiki: The Foundation of Open Source 3D Printing
• Prusa Research: Open Source Philosophy
• Digital Millennium Copyright Act Overview
• 17 U.S. Code § 512 – Limitations on liability relating to material online
• Cults3D Marketplace
• MyMiniFactory Marketplace
• Thingiverse: The Original Open Design Platform
• SFC Confronts Bambu Lab over Copyleft Compliance
• 3D Printing Manufacturer Faces Backlash Over Proprietary Locks

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

#HobbyStreak day 1338:

Ya boi Erik hath joined the realm of #3Dprinter parents. Just what I needed in my household: yet another entity that's moody, temperamental, overly sensitive and has a metric tonne of unwritten rules.

First order of business: fkn 0.2 nozzle should be easy but was Pluck&Pray😑

Second fkn order of biznitch: why does #OrcaSlicer add what seems like a non-functioning line of code to the filename output box? Can we please fkn not?😑 gcode wouldn't export

#3Dprinting #Elegoo #

Si queréis calibrar vuestra impresora 3D para que los puentes y los voladizos os salgan medio decentes, acabo de publicar un proyecto en OrcaSlicer en Printables que os va a ayudar a hacerlo. Ya que me he pegado la matada, al menos que a alguien le ahorre tiempo XD

#3dprinting #fdm3dprinting #fdmprinting #calibrating #orcaslicer

https://www.printables.com/model/1747085-bridge-flow-and-density-calibration-plates

THE CLOSED-SOURCE SHACKLE: Analyzing Bambu Lab’s Approach to AGPL Compliance

2,695 words, 14 minutes read time.

Bambu Lab took the open-source guts of 3D printing, forked the hell out of it under AGPLv3, built a slick empire on top, and then slapped a closed-source shackle around the whole damn thing. This isn’t some gray-area technicality. It’s a straight-up betrayal of the license that gave them their unfair head start. They ship printers that print like a dream while quietly locking down the machine’s soul behind proprietary walls. The RepRap boys built this industry on dirt, sweat, and full ownership. Bambu turned it into a corporate cage.

The Core Violation

The smoking gun sits right in Bambu Studio — their slicer, forked straight from PrusaSlicer under the AGPLv3. That license is brutal for a reason: modify it, distribute it, especially over a network, and you release the full source. No hiding pieces. No “optional” bullshit.

Bambu loads a closed-source bambu_networking plugin that handles cloud auth, remote control, and core features. It auto-downloads, dynamically links, and becomes part of the program. The Software Freedom Conservancy already called it what it is: a clear AGPL violation. You can’t carve out the heart of the software, close it off, and still claim you’re playing by the rules. This is license laundering, plain and simple.

They reaped the open-source commons like bandits, then built their castle walls with the stolen stones.

The 2025-2026 Escalation

When a developer named Paweł Jarczak did what real men in this space do — forked the code and restored direct functionality — Bambu didn’t compete. They lawyered up. Cease-and-desist letters, accusations of impersonation, reverse engineering, the whole corporate playbook. The fork came down fast.

That move lit the fuse. It dragged the whole mess into the open. The SFC launched a formal compliance review. Josef Prusa himself called out the unauditable black box. Suddenly the world saw what Bambu was really protecting: not innovation, but control. Their new Bambu Connect middleware pushed even more traffic through their servers, tightening the leash.

This wasn’t defense. It was panic dressed up as professionalism.

Bambu’s Defense and Why It Stinks

Bambu’s line is the usual slick corporate speak: the networking plugin is “optional,” their cloud is private infrastructure, and they love open source — just not when it steps on their turf.

The plugin isn’t optional when the slicer leans on it for basic modern functions.

AGPL doesn’t care about your marketing slides or how you label components. If it forms one integrated product — and it does — the whole thing must ship with source.

They want the credibility of the open-source roots without the obligations. Classic embrace, extend, extinguish.

No amount of smooth PR changes the fact they’re treating the community that built this industry like unpaid interns who should be grateful for the privilege of buying their locked-down gear.

The Brutal Reality

This is bigger than one company. It’s the old fight between men who want to own their machines down to the last bolt and corporations that see full ownership as a bug, not a feature.

Bambu makes hardware that performs, no denying that. But performance bought with closed-source shackles comes at a price: you paid for the printer, yet they still own part of its soul.

The RepRap era was ugly, dirty, and free. Bambu’s era is clean, fast, and leased. They didn’t invent the tech — they commodified it and put a fence around it. The AGPL drama proves they know exactly what they’re doing.

In the end, the closed-source shackle isn’t an accident. It’s the business model. And the industry that started with hackers in garages is learning the hard way what happens when the suits move in and start changing the locks.

Call to Action

So what are you going to do about it, brother?

Stand with the Software Freedom Conservancy — the crew already hauling Bambu’s AGPL violations into the daylight — alongside real right-to-repair warriors like Louis Rossmann, Kyle Wiens at iFixit, and the lawmakers grinding through repair legislation in Europe and the States. These men aren’t asking permission; they’re exposing how companies twist DRM laws — originally built to stop movie piracy — into weapons for permanent digital lock-in.

Bambu’s closed-source networking shackle and cloud middleware are textbook abuse: they take hardware you paid hard cash for, wrap it in proprietary chains, and then hide behind “security” and “user agreements” while daring you to touch what’s yours. Rossmann has spent years ripping the mask off this exact corporate game. It’s the same play — control the software, control the machine, control the man who bought it.

Ditch the cage. Support Prusa, run a Voron, back true open forks, and fund the SFC’s compliance fight. Demand full source code. Call out every violation publicly. Build loud, repair louder, and make it painful for any company that tries to lease the soul of your gear.

The RepRap spirit was born in garages by men who refused to kneel to suits. That fire doesn’t have to die just because the hardware got slick. Own your machines — every bolt, every line of code, every function — or keep paying rent on your own property.

The choice is still yours. For now. Make it count.

D. Bryan King

Sources

• GNU Affero General Public License, Version 3 (Free Software Foundation)
• Comprehensive Response to Bambu’s AGPLv3 Violations (Software Freedom Conservancy)
• The Battle Over 3D Printer Software Licensing Matters For Everyone (Aftermath)
• Bambu Lab Now Under Formal Investigation for AGPLv3 Violations (3D Printing Industry)
• Setting the record straight on Cloud Access and Community (Bambu Lab Blog)
• The Bambu Lab / Open Source Dispute Is Not What You Think It Is (Fabbaloo)
• GNU Affero General Public License v3.0 or later (SPDX)
• Why the Affero GPL? (Free Software Foundation)
• Frequently Asked Questions about the GNU Licenses (GNU Project)
• What is Free Software? (Free Software Foundation)
• Selling Free Software (Free Software Foundation)
• The Open Source Definition (Open Source Initiative)
• Open Source Initiative: Frequently Asked Questions (Proprietary Licensing)
• Securing the Software Supply Chain (CISA)
• NIST’s Approach to Software Supply Chain Security
• Software Licensing (MITRE Corporation)
• Why the AGPLv3 is a critical license (Free Software Foundation)
• NIST Cybersecurity Framework
• The GPL is a License, not a Contract (Free Software Foundation)
• Technical Challenges in Software Assurance (MITRE)
• Copyleft Compliance Principles (Software Freedom Conservancy)
• Right to Repair (Electronic Frontier Foundation)
• Words to Avoid (GNU Project)
• Fighting Your Own License Violations (GNU Project)
• Free Software Licensing Compliance (Free Software Foundation)

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Oh no, #flashforge is the next #3dprinter to #enshitify!!!! #3dprinting

The new firmware injects #ai ads into your slicer software 🤦

https://www.youtube.com/watch?v=higSOW0-N24

#LouisRossmann #orcaslicer #Foss