Depending on your use cases and apps, file locking can be problematic when sharing across SMB and NFS simultaneously, their locking semantics are slightly different
Depending on your use cases and apps, file locking can be problematic when sharing across SMB and NFS simultaneously, their locking semantics are slightly different
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.
TacticalRMM is very comprehensive, self hosted, but more geared towards organizations managing a fleet of machines.
It’s not the Muslims, it’s the evil Christians. Same problem, but different names.
It’s uncommon for ‘public use’ ethernet ports to exist, unless they are clearly labeled. The ethernet ports might grant access to the internal network, which, is easy to accidentally do. A non-profit library with a limited budget might overlook all the extra protections on open ports (enable/disable ports as needed, use 802.11x port-based authentication, internal SSL, etc), that would be necessary to secure it. Or, even better; that RJ45 port might be wired up to an old PBX, and you may have fried their telephone system, or your own hardware.
The Germans have Russians. :-/
IMAP on O365 now requires “Modern Auth”, which requires OAuth to authenticate access to mailboxes. Anything that connects via IMAP will need to be approved by the admins at this point (Including Thunderbird). Without the cooperation of your organization’s IT team, you are not going to get far.
I worry too – if this gets any significant uptake, what’s stopping Reddit from shutting off the spigot? Given their reasons for turning the screws on API and other policy changes, they may not take kindly to having “their” content re-posted elsewhere, let alone to a system designed specifically to escape reddit.
Could be too much pressure – double check your z-offset/leveling? I had it so bad, and didn’t realize it, … and wore out the original brass gear :(. The nozzle was pushed right up against the bed, so it was trying so hard to push out filament that wasn’t going anywhere.
Planka looks very promising too
TOR needs to have a lot of ‘background noise’ legit use, otherwise the folks needing to hide in the weeds stick out like a sore thumb.
If you use gitea, it’s just a few steps to enable it to be an OAuth2 provider. See Oauth2 Provider Docs
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.
As an anecdote – I have been sitting on an elastic IP at AWS for years, with reverse DNS configured properly for it. Way early on (years ago), some spam filters would block the whole netblock, but I can’t remember the last time the IP Block was wholesale blocked. I think AWS is very much on top of any spam complaints from their Elastic IPs, and as long as you don’t abuse your specific IP, you are in good shape for light volume, non-spam mail.
LMTP support would be nice too: existing mail routing infrastructure could send messages into stalwart-managed mailboxes. (Edit: reading the docs, they do support LMTP! This is awesome)
A single binary can be invoked with different privilege levels. OpenSSH, for example is a single binary, but uses OS privilege separation when setting up connections from the root-owned daemon. (Just to be clear, I’m not sure that stalwart is using this technique, just that single binary apps do not exclude the possibility of OS privilege separation.)
MoCA is a way to send wired Ethernet up to (300mb/s, at least the version i have) over coax. Verizon fios would provide these devices to send internet to set top boxes over existing coax cabling, but you can get a pair of these devices and send Ethernet in on one side, and Ethernet out the other side.
I have noticed however, it adds a bit of latency to the connection, which may be trouble.