Is this loss?

Price fixing is a problem because of the power imbalance between businesses selling products, and individual consumers that need to buy them.

Worker unions are a solution to that power imbalance.

They are also using this as an excuse to get customers on their data hoovering apps to get access to any of the best deals.

At $dayjob I switched from Apache to nginx 15+ years ago. It’s Callback/Event based process model ran circles around Apache’s pre-fork model at the time. It was very carefully developed to be secure, and even early on it had a good track record. Being able to have nginx handle static content without tying up a backend worker process was huge, and let us scale our app pretty well for the investment of time. Since then, Apache implemented threaded + Event based process models, Caddy, traefik, and a bunch of others have entered the scene.

TBH, I think the big thing nowadays is sane defaults, and better configuration, even automatically discovered configuration – traefik is my current favorite for discovering hosts in consul/Kubernetes/simple host definition files, but since traefik can’t directly serve files, I simply proxy from traefik to … nginx :)

Navidrome is another server that works pretty well, implements the subsonic protocol ( so all the apps that can cache and stream to your mobile device work). You can have multiple logins, or just share out playlists and albums individually to non-authenticated users.

Paige, no, no, no, no, no!

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.

Delta Chat just a clever chat interface over SMTP/IMAP, and thusly every user can use their own mail server for sending + receiving messages. Any encryption is between the end devices, and to cooperate, they’d have to produce a compromised build that leaks those keys.

⟋etc⟋passwd ⧸etc⧸passwd ／etc／passwd

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.

Is this about elles ?

TacticalRMM is very comprehensive, self hosted, but more geared towards organizations managing a fleet of machines.

Don’t UWU! That’s a $350 fine!!!

“Goodbye, Earl!”

It’s not the Muslims, it’s the evil Christians. Same problem, but different names.

The Germans have Russians. :-/

Passkeys are great, and generally a plus for security; but (a) all the most popular implementations have not implemented key export and transfer to alternate implementations (b) It includes an implementation ID + hardware attestation feature which can be used to disable ‘unapproved’ implementations by key consumers. Considering the most common device with a ‘secure’ environment, and can implement this are your cell phones, and they are made by Apple + Google, this effectively locks your identity to either of these platforms. © All the public signals smell and look like the providers (apple, google, Microsoft) are doing everything they can to implement the features to make lock in all but inevitable, including mandating that implementations user-hostile features, or risk being rejected by sites.

It’s a great idea, and it could be awesome, but things are not being addressed. Or being handwaved as “we can address them later”. This recent discussion from last month (both the discussion in the linked github issue, and in the HN thread both including some key players in the PassKey system) is pretty telling: https://news.ycombinator.com/item?id=39698502