1. https://gotify.net/

2. https://shoutrrr.nickfedor.com/v0.17.0/

3. https://github.com/caronc/apprise

I wish I had more time and I'd throw Calibre at it.

Circuit designers use these tools basically daily for two reasons - the first is Layout Versus Schematic. We want to make sure that the physical layout matches the schematic, so the tool turns the layout GDS into a netlist and compares that to the netlist created from the schematic (basically a diff, but more complicated). The second is so we can run simulations that take into account the "parasitic" resistances and capacitances of the wires and metal shapes in the physical layout. It's basically the same procedure as LVS with an extra step that analyzes the metal shapes to determine said R's and C's.

I deploy docker compose files with ansible so everything comes with built in security defaults like rootless, dropped caps, no new privileges, etc. I wish more containers supported running read only (its usually pretty easy to add, just overlooked) and distroless (common for go apps, less so otherwise).

There was a pretty good comment on reddit a while back with a list of hardenings for compose files [1]

1. https://www.reddit.com/r/selfhosted/comments/1pr74r4/comment...

I really liked using Fleksy which let you swipe up and down on the keyboard to change autocorrect results, including adding words to your dictionary. I'm still not sure if FUTO even has that option.

It's also probably worth pointing out that Lego was nearing bankruptcy and was saved by a ton of licensing (and Ninjago, to be fair). Fortunately, they've used that income stream to still consistently put out a lot of high quality first party sets. Hopefully WotC doesn't lose sight...

I've noticed more and more open source projects recommending timers as a deployment method and I think that's great!

I think the "paradox" is that you'd expect disadvantaged students to perform worse on standardized testing.

Something funny is up; this doesn't seem deliberate.

But that's just not true? You can connect a printer in LAN/dev mode and print directly from slicer to printer. There are apparently some issues with more complex network setups but that seems to be the exception rather than the rule.

I think the concerns he has generally are valid, but I have yet to see something from a legal perspective (e.g. precedent) that convinces me this constitutes a license violation. Would love to see one.

Similarly, it seems, though they didnt exactly say, that they're running bun with a warm package cache... What about the others? Do they have caches?

How is this enforced?

More likely, it's technical incompetence. It's just easier (for their cloud) to send everything through their cloud

A different way of looking at it is that Bambu is saying if you want to use their cloud you have to send everything through their cloud. Stupid? Sure. It's very much a technically solvable problem. But I don't think there was any rug pull (this time; in Jan 2025 they tried...)

I think this is all more out of incompetence than malice. Something bad happens, exposing wildly inadequate programming expertise, they panic and over correct, and the community pushes back. They're great at making 3D printers, terrible at cloud infra.