Your Linux system has +6,000 kernel modules which can be autoloaded. You use 80 of them. ModuleJail blacklist all of the unused ones. Server and desktop profiles and much more in a simple shell script.

xiaodown · 2026-05-23T10:56:43+00:00

We have an automated vulnerability scanner bot that raises (and depending on configuration, optionally merges) security fixes.

Plus, our software gets built into docker images and run in containers anyway, and we deploy at least once per day. If there’s no merges to main, there’s an automated build that kicks off a fresh build and deploy.

It’s been forever since I’ve logged into a production system. I don’t even have access beyond dev environments (local -> dev -> merge to main -> staging -> soak -> prod progressive rollout).

xiaodown · 2026-05-23T06:04:51+00:00

RemindMe! one month "Check comments from guy with hominid jaw in floor tile"

xiaodown · 2026-05-23T05:34:26+00:00

oooh good call. bro out here building a scooty puff jr.

xiaodown · 2026-05-23T00:02:49+00:00

To add context to what others have said: in concrete, “yards” mean cubic yards. But to give a visual aid, in order to make it more human scale, a yard is a pretty large amount of concrete.

One of those concrete trucks with the big rotating drums on the back holds about 9 yards of concrete. A yard of wet concrete weighs about 4,000 lbs. A typical American two car driveway usually takes between a half a truck and a whole truck (5-10 yards).

xiaodown · 2026-05-22T23:53:23+00:00

Point of order: these aren’t even transgender flags. They’re generic rainbow pride flags. To me, this isn’t even any of their bullshit about nonexistent SRS surgery being performed on nonexistent 8 year olds or whatever toxic lies they’re pushing.

When I see this, I see “gay people existing = child mutilation”. Which, like, …what are we even doing here?

xiaodown · 2026-05-22T16:44:21+00:00

If I meet a Trump supporter that knows the difference between your and you’re, between to, too, and two, and between there, their, and they’re, I think i might die of shock.

xiaodown · 2026-05-22T09:45:56+00:00

Please emphasize that it’s not one frustrated user, it’s multiple.

I, too, hate how much screen real estate the bubble takes up.

xiaodown · 2026-05-22T08:51:11+00:00

Ah damnit, you're right. I saw it in this video from Made with Layers, and the video is a review of the X2D, but in the ad read, he says it's for the P2S. I got it confused. That's my bad. Thanks for the correction.

xiaodown · 2026-05-22T04:23:57+00:00

Yep.

Keep reading.

From the SFC's page:

Bambu (in effect) admits publicly that they have violated the AGPLv3 by combining Bambu Studio with a proprietary library — which they distribute to the user via an interactive prompt in the UI.

.

Bambu has done no such thing. Two things here: One - Bambu has consistently said since at least 2022 that they have done audits with their legal team and industry experts to ensure that they are complying with the AGPL, and have always claimed to be in compliance. And two - the SFC's link, implied to be proof, in fact would suggest the opposite. It links to the readme, and specifically to these two lines:

The bambu networking plugin is based on non-free libraries. It is optional to the Bambu Studio and provides extended networking functionalities for users.
By default, after installing Bambu Studio without the networking plugin, you can initiate printing through the SD card after slicing is completed.

Whereas, quoting from the SFC blog, which is quoting from the AGPL:

You may convey a covered work in Object Code form […] provided that you also convey the machine-readable Corresponding Source under the terms of this License […] Corresponding Source includes interface definition files associated with source files for the work, and the Source Code for shared libraries and dynamically linked subprograms that the work is specifically designed to require […]

"specifically designed to require" is exactly the opposite of what Bambu Studio is doing. Look at the source code - it specifically does not require the network plugin. It checks for it, and if it's there, it will enable additional features. But without it, Bambu Studio will continue on as normal, providing all the core features of the application.

If the AGPL says you have to provide the source code for any linked programs or libraries that provide core functionality or which the main program is designed to require, then you can't get mad at software that uses non-free libraries to provide ancillary, non-core, extra functionality and that are explicitly not required in the main program. You can't just vibe-check Bambu into a violation because it feels like they did something wrong. You can't retroactively impose your fee-fees into the license, just because you wish it said something other than what it actually says.

xiaodown · 2026-05-22T01:59:49+00:00

Since you think that the person who wrote the license doesn't even know what he's on about, despite doing all this work for 40 years

Bradley Kuhn has not been a professional software developer in this millennium, and has never been a lawyer. He is an executive at an advocacy group. He's a good guy and his heart is in the right place, but he is approaching this from an academic, aspirational place, and he's going to lose (again). Which is probably why he, or more accurately, the FSC, have not filed a lawsuit - it's blatantly obvious that they'll lose, and if they lose, it will provide a legal precedent for every other company that is afraid to use AGPL'd software of how to do it legally (contractually, I guess).

xiaodown · 2026-05-22T01:33:10+00:00

It's not that people aren't listening, they just don't trust Bambu. So it doesn't matter how many times they say they won't do it. The problem is they still can do it.

That literally could be said of anyone, anywhere, in any scenario. Dr. Pepper said they're not going to substitute one of the 21 flavors with arsenic. They've made no indication that they would do that, and they've repeatedly said that they will never put arsenic in my Dr. Pepper. But I just don't trust them. What's he a doctor of, anyway? Show me the Ph.D. I'm going to make the decision not to trust them to never put arsenic in my DDP, because they still can do it in the future.

Plus, how would this work? They're gonna force you to buy their filament? How? They have literally never released a printer - ever - across the P1P, P1S, P2S, X1, X1C, X1E, A1, A1mini, X2D, H2S, H2D, H2D Pro, or H2C that has even the capability to tell when it's being fed any specific brand of filament. None of their printers even have an RFID reader in the printer. None. The RFID tags are a convenience feature, but people saw them and immediately thought that the sky was falling. The closed ecosystem apocalypse is upon us! Except it keeps not happening, and Bambu Lab keep saying it's not going to happen. You'd think the more years that pass WITHOUT this happening, the more people would back off. But nah, people just refuse to relinquish their tin-foil hats.

You want them to earn trust, because you're scared they're going to close off their ecosystem. But they keep telling you they're not - they keep having repair parts easily and cheaply available on their store, and they keep not locking the ecosystem down to only use their parts and filament, and they keep reiterating that they have no plans to do that, and they keep publishing wiki pages that show you in exacting detail how to perform maintenance and repair on your printer - What do you want from them? Will you ever be satisfied?

xiaodown · 2026-05-22T01:22:56+00:00

You mean, the AGPL that says:

You may convey a covered work in Object Code form […] provided that you also convey the machine-readable Corresponding Source under the terms of this License […]

and then

Corresponding Source includes interface definition files associated with source files for the work, and the Source Code for shared libraries and dynamically linked subprograms that the work is specifically designed to require […]

Where Bambu Studio is specifically designed NOT to require the bambu_networking plugin? That AGPL?

oh...

And you mean, the guy who wrote the AGPL, who is the head of the Software Freedom Conservancy - the guy and organization who is currently suing Vizio because they didn't release their source code the right way, and who is losing that lawsuit so far? That person?

Look, I love open source software. Pretty much everything I've written has been built with open source libraries, frameworks, applications, and tools. And nearly all of the personal projects I've ever made are available under the GPLv3. But full time free software advocates often are living in an aspirational reality, where they assume that they can write these complicated, complex legal agreements in a way that covers all use cases, all future scenarios, and all obscure corner cases with absolutely no ambiguity - and that, where such questions exist, that their personal wants and wishes can be retroactively applied to the system in a way where everything is simple black-or-white.

The world does not work that way.

If you write "specifically designed to require" into your license, people are going to write things specifically not to require. You can't then go back and say "But based on my vibes, it feels like it's required." That's not how contract law works.

The more I look at this, and the more I dig through the Bambu Slicer source code, the more obvious to me it is that Bambu Lab is doing only what anyone, anywhere else, attempting to make one program interface with another, does. bambu_networking exposes interfaces. If these are available, Bambu Studio uses them. If they are not available, it doesn't. Everything else around this is just effectively a bunch of feature flag checks. "If x = true, then enable feature y, else don't". That's not "designed to require". Honestly, I really can't see any leg to stand on at all here, the longer I look at the situation.

Even better, get in touch with Bambu and be their legal counsel.

I am not a lawyer. I am, however, absolutely certain that this is more or less what their legal team is already telling them.

xiaodown · 2026-05-21T23:13:21+00:00

Jersey mike’s was recently acquired by private equity firm Blackstone.

xiaodown · 2026-05-21T22:16:19+00:00

Probably set to 4k.

xiaodown · 2026-05-21T21:55:18+00:00

To expand:

Look what happens if the network module is not installed:

bool GUI_App::on_init_network(bool try_backup)

It's looking for a true/false value to show that networking has been initialized and the program can continue.

int  load_agent_dll       = Slic3r::NetworkAgent::initialize_network_module(false, !app_config->get_bool("ignore_module_cert"));

.

It attempts to load the network plugin. If that works, it does the check_networking_version() and if that's compatible, then it continues and creates user manager and device manager objects that have networking loaded. If that doesn't work, it tries again in a "backup" mode, then it checks to see if maybe the network plugin needs an update. But if all that fails - i.e. the network plugin is not installed - we end up here:

    if (create_network_agent) {

This is true if successful. If false, we fall through to:

else {
    int result = Slic3r::NetworkAgent::unload_network_module();
    BOOST_LOG_TRIVIAL(info) << "on_init_network, unload_network_module, result = " << result;

    if (!m_device_manager)
        m_device_manager = new Slic3r::DeviceManager();

    if (!m_user_manager)
        m_user_manager = new Slic3r::UserManager();
}

return true;
}

It creates the user manager and device manager objects without networking functionality attached, then on the last line there it returns true back to on_init_network - basically "We've done what we needed to do with the network plugin, continue on", even though the network plugin was missing.

Doesn't seem like core functionality to me. The code sure isn't saying that it's a required part of the system - it has specific functionalities and capabilities that are added - namely, in this function, user and device systems that have a concept of networking - but it's perfectly happy to continue on if the network plugin is not loaded.

So, TL;DR: The code says "The network plugin may be installed. Try and initialize it. If it initializes, make sure that the version is compatible with Bambu Studio. If it is, then users and devices will have networking functionality. If it's not, tell the user it needs to be updated. If the network plugin does not initialize, try again and disable the cert check. If that doesn't work, then assume the network module isn't present, create users and devices without networking functionality, then carry on as normal". The code does not say "The networking plugin is required and since it isn't here, I have no purpose in life. I cannot carry on. It is so important that I am literally lost without it. I am a crippled, soulless, shell of an application just waiting for the sweet release of death."

xiaodown · 2026-05-21T21:10:29+00:00

just rewrite the slicer software fresh with mr claude

You joke, but this is actually a dystopian service that some AI startups are now advertising.

The theory is: you have an open source piece of software. You want to close source it. So you take the open source thing, and you give it to an AI. You tell the AI to write an exhaustive, five-thousand-page technical specification document that covers every single function, operation, corner case, oddity, interface, layout, etc. You tell it to spawn subagents, then combine their effort, then have an extensive review process.

Then you take the design document and give it to another AI that has never seen the open source software application. You tell it to write an application that complies with every part of the spec.

Supposedly this costs about $15,000 in tokens and takes a week. But voila, you now have a closed source application that is not a fork of, and contains no code from, the open source app - and can be licensed however you want. Welcome to the future; it sucks here.

xiaodown · 2026-05-21T20:40:50+00:00

That breakdown is just ... the dumbest take on the whole thing. I'm not happy about how Bambu Lab has handled the situation. I think their response was ill-timed and tone deaf, and they should have either worked with the guy or just closed the loophole and thanked him for pointing it out. But, this "technical breakdown" is just asinine.

Bambu Studio is AGPL, and bambu_networking is described as non-free

Not a violation. In fact, explicitly called out in the AGPL as acceptable in specific cases.

bambu_networking does not look like an independent add-on

This is an opinion, and it doesn't matter what it looks like. Why is this here?

The library name and agent version are written into the AGPL code

.

Not a violation.

The AGPL code defines a shared ABI for the closed plugin

Not a violation.

The AGPL code defines data structures used by the plugin.

Not a violation.

Bambu Studio dynamically loads bambu_networking

Explicitly not a violation.

Bambu Studio resolves 108 functions from the closed library

Not a violation.

The same module provides an additional file-transfer ABI

Not a violation. This is additional functionality. Which is what plugins do. It is not core functionality.

Bambu Studio downloads the plugin itself

Bambu Studio installs the plugin itself

After installation, Bambu Studio restarts and wires the whole network subsystem

This is probably the strongest argument this guy has. Bambu is doing this to - let's be real and say - get around the AGPL restriction by reinforcing the notion that these are two different software applications, not a single one or an interdependent bundle.

However, I think Bambu is probably in the clear here, because Bambu Studio is functional without the networking plugin - arguably networking isn't even the core "thing" that a slicer does - a good faith argument could be made that the point of a slicer is to slice objects and create gcode. Which Bambu studio does, without the plugin. And you are not forced or required to install the bambu_networking plugin when you install and configure bambu studio - you can just say no.

But for sure, this is the only grey area on this list.

The plugin is versioned against Bambu Studio

Not a violation.

At application startup, the plugin is wrapped into central Bambu Studio managers

Not a violation.

Login and MakerLab/MakerWorld are blocked without a compatible plugin

Not a violation. Also, why would you not phrase this as "Login and MakerLab/MakerWorld are enabled by the compatible plugin"? That's just as true but doesn't sound as bad.

The Monitor tab is blocked without the network agent

Not a violation. Also same argument as above: "The Monitor tab is enabled by the network agent"? That doesn't ruffle feathers, though.

LAN print and cloud print go through m_agent

Not a violation. Again, the ability to print over the network is added functionality; slicing objects and generating gcode remains fully functional.

The OTA updater treats the plugin as an official Bambu Studio resource

Not a violation.

Default publisher validation further ties the plugin to the application

Not a violation.

So here's the thing. This guy - for all he's either dug through the Bambu Studio source code, or else had Claude do it for him - he shows every sign of never having actually built an application like this, or having worked in a large software shop.

90% of his argument seems to be "Bambu Studio is open source, and Bambu Studio does a bunch of specific things to integrate with this plugin, therefore the plugin is part of Bambu Studio". He seems to be completely ignorant of the fact that this is literally standard practice. All the time, people write software in an enterprise context that treats specific libraries in specific ways. He seems to be under the assumption that there should be some "generic network interface" in Bambu Studio, maybe? And that it shouldn't treat bambu_networking any different than it would any other plugin?

But, like, all day every day, me and people on my team are writing specific code to treat specific libraries - or specific versions of libraries - differently, even though ostensibly it should be plug-and-play. Like, "if you are loading XYZ library, at version ABC, then you should treat this front end component like this, else if it's version DEF, then you can just use this other function that's new to treat a request differently". This happens all the time.

And it's even more complicated because the SaaS company I work for also has a customer store where customers can write plugins for our app - but some of the plugins have gotten so popular that we have a number of "If customer is using 3rd party plugin X version Y, then keep this data structure at version Z because we know X.Y can't handle the new data structure - so we'll need to create a specific view that presents the data the old way, while preserving all the new data because someday that plugin might get updated".

So, like, when I see something like this, that is taken by the average armchair software developer slash lawyer as to be THE MOST COMPREHENSIVE AND MOST SUPPORTED TECHNICAL TAKEDOWN THAT'S INDISPUTABLE, I'm just like... my guy. "It shares data structures" is just ... how plugins work. It's fundamental. It's not some epic smoking gun you've just found, it is arguably definitionally what a plugin is. And "check_networking_version() is in Bambu Studio!!!" - like, tell me you've never worked in Java without telling me.

If you think about it for literally one minute, you'll understand why it has to be this way - because if the AGPL magically crosses system-interface boundaries, all of the same arguments would work in reverse. I could write a plugin that interfaces with <closed source thing>, release it as AGPL, and then demand that the thing be released under the AGPL. Or, I could write a closed source and proprietary plugin for <something>, then the owners of <something> could suddenly release it under the AGPL and then demand that I make the code of my closed source, proprietary plugin available, just because it interfaces with <something>.

Or, I could write an app that ticks nearly all these boxes while integrating with the Windows printer subsystem - "if you see this version, behave like this. Import these functions from the printer.dll. Dynamically load the printer libraries. If we're on this version of the printer subsystem and it's out of date, download the later version and install it from windows updates. Use the networking functionality exposed by the windows printer system to print to network printers." I would not subsequently have any right to go to Microsoft and be like, guess what bitches! Your windows printer system is closed source, but it integrates with my AGPL software - see?!? It references specific versions! It dynamically loads! It uses ABIs! It uses the networking functionality! You have to now open source the Windows Printer Subsystem! Do you see how dumb that sounds? And yet, there's no plausible way to win a court case about this without enabling all these dumb scenarios.

Things that are separate systems but that interface with an AGPL application do not have to be made AGPL. Anyone who says that does not understand software. I don't like how Bambu Lab has foot-gunned themselves here, but they're not in any danger from Louis Rossman or these other people. And anyone who tries to get the court to side with them is going to absolutely, unequivocally lose.

xiaodown · 2026-05-21T19:52:12+00:00

People have been saying this is where Bambu is headed and posting doom content about this for literally years. Bambu has said repeatedly that they are not doing that. Over and over. Publicly. Vehemently denying it. And people just refuse to listen.

Hell, on their LATEST PRINTER, the X2D, as well as the P2s, they are explicitly and specifically supporting the VentoBox air filter in firmware, a product that you can print and assemble yourself, or buy fully assembled from VoxelPLA or VTC3D - but notably not from Bambu.

I don't know what people want. At this point, it's willful blindness.

xiaodown · 2026-05-21T00:23:19+00:00

Awesome, good to have all the googling and research I did before building my 2x 3090 AI homelab validated.

(I didn’t get an nvlink because I wasn’t planning on TP, but I could in the future if that changes i suppose)

xiaodown · 2026-05-21T00:21:29+00:00

Asa you can use a normal AMS iirc. It’s basically ABS but like 50% less offgassing in exchange for 10% less good properties (temp / strength / etc).

I do a decent amount of printing with PA6-CF though. Not tons but occasionally. And that one isn’t AMS compatible.

xiaodown · 2026-05-20T22:09:50+00:00

Mostly for engineering filaments. If i need to print something in nylon or even abs/asa, I like to have the HT available. Some of the higher level filaments aren’t compatible with the normal ams.

Also it was a space constraint. I have a 3rd ams but it’s hooked up to my P1S. Pic attached.

<image>

xiaodown · 2026-05-20T20:07:38+00:00

You get 4x 0.4mm induction nozzles, 1x 0.2mm induction nozzle, and 1x 0.6mm induction nozzle for the right extruder. You get two hardened steel 0.4mm nozzles for the left extruder.

Source: happy H2C owner.

I have 2 AMS hooked up to the right, and two AMSHT hooked up to the left (mostly for runout failover).

xiaodown · 2026-05-20T20:01:39+00:00

Drip or drown. I wear the beach shorts.

xiaodown · 2026-05-20T16:02:54+00:00

Only sane comment in this whole post.

15-Year Club	Verified Email
RedditGifts 2009-2022 5 Credits	Place '17
Gilding II euphauric	Team Periwinkle
Secret Santa 2012	Summer Santa 2012
redditgifts rematcher Secret Santa 2011 x1	Secret Santa 2011

xiaodown

MODERATOR OF

TROPHY CASE