This part gives me hope, but I have not been able to find the certificate:
Option B: cloud mode without Developer Mode
Starting with v2.0.0 the plugin can also drive a cloud-paired printer with verification left ON — no Developer Mode. This keeps the cloud features (cloud print dispatch, print history, MakerWorld) but is meant for advanced users, because it requires private slicer credentials that this project does not distribute.
Two things are needed:
1. Bambu's slicer credentials, which you provide yourself. Put slicer_cert.pem, slicer_key.pem and slicer_crl.pem in the plugin's config directory (or point at them with slicer_cert_pem / slicer_key_pem / slicer_crl_pem in obn.conf). The plugin uses the key to sign MQTT print commands and to install its app certificate on the printer. These are private credentials. This project does not ship them and gives no instructions on obtaining them — you have to find or extract them yourself, and you alone are responsible for ensuring your use complies with the applicable terms and law.
2. Two settings in obn.conf. Set block_cloud = 0 (the default 1 blocks cloud printing outright) and client_name = BambuStudio (the honest default client name is rejected by the cloud print API with HTTP 403).
With that in place you get signed MQTT commands, on-printer app-certificate install, cloud print dispatch, print history and MakerWorld — without touching Developer Mode.
What the default cloud_print = cloud_only actually uploads. Even in this mode the model itself normally stays on your network: for a print with a cloud record the plugin sends the .3mf straight to the printer over LAN FTPS, and only the record goes to Bambu — a project entry, a task entry (mode=lan_file) and a small config .3mf that print history uses for its thumbnails. That record is exactly what buys you the cloud extras: print history in Studio and Handy, and the ability to rate models on MakerWorld. The full model is uploaded to Bambu's servers only when Studio dispatches a pure cloud print (start_print), e.g. for a printer that is not reachable on your LAN.
You can limit even that: set cloud_print = try_lan_first or lan_only to print over the LAN without writing a cloud record at all, and cloud_hide_history = 1 to hide the cloud print history in Studio.
If you run neither Developer Mode nor valid credentials, the printer rejects every print / project_file command and shows on its screen:
There's been 40 years of documented push back when western governments try to backdoor things - starting with clipper. Pushback is not always successful - but it's far more transparent then China.
Probably, but you are asking the wrong question: Is it legal to produce non-backdoored networked devices or services in China?
The answer to that question in the US is within epsilon of “no” thanks to the cloud act.
Europe and China have passed similar laws. However, China has a reputation for passing laws then selectively enforcing them. Maybe if you get on the right side of the right party member, the answer might still be “Yes” there.
Anyway, the next question to ask is: Who would I rather backdoor my device?
I doubt the Chinese government cares much about me, and unless I vacation there it’s an international incident if they, say, hack my car and murder me by aiming it at a tree at 95mph, like the CIA apparently does now:
Of course, the US government banned cars from China. Presumably this is because they do not have the mandated remote murder network port open, or, if they do, the US doesn’t have the necessary permissions to access it.
Those are both great examples. I think this doesn't obliterate my point, though it weakens it. The manufacturer in CVE-2026-11405 is already out of business, and the one in CVE-2026-66747 is unlikely to continue as a going concern.
Would Xiaomi or the CCP accept the reputational and legal risk of getting caught with a backdoor? Recall the CCP considered the arrest of the Huawei executive in Canada as an offense against itself.
Like a stopped clock, Fox News is right once or twice a day.
For instance election tampering in the US is a well-documented thing: However it almost always favors republicans in districts with electronic voting machines that do not generate paper trails.
As for the person you are replying to, their claims have been documented by most media outlets, places like wikileaks, and their claims are backed by US legal requirements to backdoor stuff (like the US Cloud act).
from the Summary -
ALL monetization across my entire channel has been disabled because of Google's faulty AI and a 'known' glitch within their system. They refuse to offer any way to resolve it. It's also happening to countless others. It could happen to you or your favorite YouTuber. Let's get this out there and pressure Google to fix it.
This is commonly repeated, but if you go look at actual record keeping - at the history of early North American and Caribbean/Bahamas colonization through the period where there stopped being as much cross-cultural contact - we see epidemic after epidemic wipe our colonials as much as any. The mortality rate is staggering - even places that should have shown this the most - Haiti for example, the documented evidence was far closer to 100% mortality to Europeans, and significantly less for indigenous. Coming to Haiti during the Haitian revolution was a death sentence for all of the people who lived in squalor in one of the densest cities in Europe - Paris.
Cultures coming together historically were deadly. There is a school of thought that argues that the Persian and Roman downfall was directly associated with the ability of diseases to transit roads.
Of course, this is the stuff that we have records for. It's possible that there was a undocumented mass extinction event, But I tend to be skeptical of historical claims that are based on extremely localized and limited archeological projections.
Well regardless, we know North American natives had extensive sanitation practices and epidemics were quite rare. Syphilis, tuberculosis, intestinal parasites, and Chagas disease were all present but rarely turned into mass outbreaks.
Mass graves are almost completely absent and life tables show steady and predictable mortality curves over centuries
I find it hard to believe that Europeans living in close quarters with livestock didn't result in increased rates of epidemics tbh but I'll take your word for it
I didn;t say that it didn't - in fact, the reality was mass casulty events where common in a way that is unthinkable. We do _ in fact_ have plenty of mass graves for colonists. The lack of evidence of the same on the American Indian side makes me skeptical of the whole narrative.
i think it's quite likely that the casualties where in similar scope across two different civilizations, but that the colonialists advantage (if you can call it such) of excess population and higher density of settlers, meant that the colonialists simply outlasted a far smaller population group.
You’re doing a lot of heavy lifting with this word colonist. The mass graves are either “imported criminal” (being in debt was a crime) or slave populations.
And it was much more about the horrid working conditions that these forced laborers were forced to work under.
What do they benefit from taking down any government, NGO or civic work program? American systems, as well as larger European systems are constantly attacked. I've seen the same traffic. Fire walling off China, North Korea and smaller eastern European countries is a must if you ever plan to expose any internet exposed services.
At the risk of noting that this is a PR statement from someone who needs something from AMD - you do realize that you just shat upon the CTO of the largest possible consumer of a technology talking about that technology? It's not 2022 anymore.
Just pointing out, there is a reason the large LLMs keep working to try to make it so their own tools can't attack their own moats, by preventing the exact behavior that you dismiss above.
I have a DGX and a Ryzen AI Max 395 - while I love both of them, there are a few critical things that leave the DGX in use, while the Ryzen "just" is my primary homelab server. The biggest thing is prefil numbers, and the performance impact of higher context sizes. Qwen 27b is a great model, nemotron is decent, gemma is workable. But all of them need reasonable context for reasonable outputs.
Unfortunitly, as others have noted, the DGX OS experience... sucks. My hope is that the RTX Spark (which looks to be the exact same stack, sans the high capacity network interface) will help this get a bit more attention, but nVidia's long long long war with the open source community is not helping. Focusing on mainlining kernel support would go a long way to getting the community to be supportive.
Of course, a massive regression just hit Linux 7+/7.1 plus for ROCm hosts, so it's just rough everywhere.
Option B: cloud mode without Developer Mode
Starting with v2.0.0 the plugin can also drive a cloud-paired printer with verification left ON — no Developer Mode. This keeps the cloud features (cloud print dispatch, print history, MakerWorld) but is meant for advanced users, because it requires private slicer credentials that this project does not distribute.
Two things are needed:
1. Bambu's slicer credentials, which you provide yourself. Put slicer_cert.pem, slicer_key.pem and slicer_crl.pem in the plugin's config directory (or point at them with slicer_cert_pem / slicer_key_pem / slicer_crl_pem in obn.conf). The plugin uses the key to sign MQTT print commands and to install its app certificate on the printer. These are private credentials. This project does not ship them and gives no instructions on obtaining them — you have to find or extract them yourself, and you alone are responsible for ensuring your use complies with the applicable terms and law.
2. Two settings in obn.conf. Set block_cloud = 0 (the default 1 blocks cloud printing outright) and client_name = BambuStudio (the honest default client name is rejected by the cloud print API with HTTP 403).
With that in place you get signed MQTT commands, on-printer app-certificate install, cloud print dispatch, print history and MakerWorld — without touching Developer Mode.
What the default cloud_print = cloud_only actually uploads. Even in this mode the model itself normally stays on your network: for a print with a cloud record the plugin sends the .3mf straight to the printer over LAN FTPS, and only the record goes to Bambu — a project entry, a task entry (mode=lan_file) and a small config .3mf that print history uses for its thumbnails. That record is exactly what buys you the cloud extras: print history in Studio and Handy, and the ability to rate models on MakerWorld. The full model is uploaded to Bambu's servers only when Studio dispatches a pure cloud print (start_print), e.g. for a printer that is not reachable on your LAN.
You can limit even that: set cloud_print = try_lan_first or lan_only to print over the LAN without writing a cloud record at all, and cloud_hide_history = 1 to hide the cloud print history in Studio.
If you run neither Developer Mode nor valid credentials, the printer rejects every print / project_file command and shows on its screen:
MQTT Command verification failed err_code: 84033543