I think it’s not widely front-and-center because it’s kinda fiddly, especially with folks with customized printers and there are caveats that can damage the machine or ruin the print if you are not careful. Sadly, I think that some of the more ‘closed’ slicer/printer systems could support it more reliably because the dimensions of the head + arm are much better known and the tool path can be planned much more precisely.

https://help.prusa3d.com/article/sequential-printing_124589 <-- explains how to set up the sequential printing in Prusa.

https://www.klipper3d.org/Exclude_Object.html <-- Explains the exclude object function in Klipper/Mainsail

https://docs.mainsail.xyz/overview/slicer/prusaslicer#enable-exclude-object <-- how to configure Prusa to label objects so mainsail/klipper can individually select and skip them.

Like I mentioned, I have the most experience with Prusa + my Ender3 ( w/ a RPi3/Kilpper & mainsail; and a crtouch sensor) . I’d wager that other slicers could do this too, but I"m not sure of their setup.

Keep in mind that if you slice multiple parts to be printed at a time, then a failure on one part means the whole batch is potentially compromised.

I have the most experience with PrusaSlicer, and have used the multiple part one at a time option to print multiple parts at once. You have to tell it the dimensions of your extruded head, so it doesn’t crash the part , and if you have a bed slinger, you have to be careful of your x axis bar (ie, order it so it starts at the front if the bed and works it way to the back)

With mainsail and klipper, you can cancel one failed part mid print and keep going on the rest of the parts.

Not only do they not federate, they also seem to suggest they are not making the self hosting option as easy as it could be because they would prefer one instance that everyone connects with.

It seems pretty solid otherwise, and the self hosted option can work if you are willing to spar with it, but that position makes it super easy for one organization to buy or somehow influence all the primary devs and turn the project closed in no time at all.

Personally, I will use both: On servers with fixed network connections I will tend to use ifupdown; but on my linux laptops I’ll use networkmanager or networkd which tend to have nice UI’s for joining various forms of wifi networks. On my laptops for some VPN’s i"ll use the ifupdown configuration, which lets me setup all sorts of exotic configurations (bridges, vlans, vxlan, vpns, namespaces, etc.) The linux command line tooling has a litany of functions to check/test/diagnose/tweak networking settings, and they work across all the distros, AND they can reveal the full details of the network, as the kernel sees it. NetworkManager, networkd, connmann, etc, often omit details in the name of simplifying for the most common scenarios.