ppchain

I watched a technology connections video that explained Hybrids in a way I hadn't heard before. Basically the gist was that because ICE cars need to be able to handle a wide range of operating conditions (accelerating uphill, creeping in traffic, coasting at 60), there are design constraints on the engine that a hybrid engine doesn't have. A hybrid battery can smooth out rapid bursts of power and recharge during less intense moments. The result is a hybrid engine can run in its most efficient speed most of the time (and apparently have a different design altogether that is more efficient somehow)

Ultimately even after conversion losses a hybrid can be more efficient than just directly driving the wheels. I think most people understand that part but the reason behind it was never obvious to me.

In the Linux ISO community the math is different because none of the data is essential, however there is a lot of it. Backing it all up even one time to an off-site location would be a 2x expense for a hobby. So 3-2-1 is hard to justify.

Instead the math can be different e.g. it's ok to lose some data but not all. Therefore you might prefer the unraid approach over zfs where losing more than parity doesn't kill the whole pool.

Not that trying to repackage and possibly resell existing work isn't a little lazy and borderline scummy, but your filter list "brands.txt" is MIT licensed.

You could always release the plugin code MIT and keep the brands.txt file proprietary or under a more restrictive license if you don't like what they are doing. After all, you did explicitly allow this.

The issue described in the post is an example of when you cannot just rely on Unix timestamps. Specifically it comes down to which date is authoritative.

A appointment with your dentist at 2pm Pacific Time in December 2026 has changed Unix timestamps in British Columbia. The dentist doesn't care about the Unix timestamp, she cares about the wall clock local time when you arrive for the appointment.

There are two reasons to be mad here and you only covered one. The first is that Bambu is trying to remove (for the 2nd time) features from existing printers.

The 2nd thing, and the reason the linked repo is now hosted by Louis Rossman (YouTuber / Consumer Rights guy) is that Bambu are abusing the AGPL license of the original slicer code. TL;DR is that Bambu Slicer is a fork of an AGPL lineage of similar tools. The gatekeeper of the cloud features hosted by Bambu was a user agent string embedded in the AGPL code. The original dev of the linked repo just copied and pasted AGPL code, and Bambu sent a cease and Desist. At least Louis Rossman believes that violates the AGPL terms against additional restrictions which is why he is hosting the repo, because the original dev was chilled from wanting to deal with the legal threats.

The point they seem to be making is that AI can "orchestrate" the real world even if it can't interact physically. I can definitely believe that in 2026 someone at their computer with access to money can send the right emails and make the right bank transfers to get real people to grow corn for you.

However even by that metric I don't see how Claude is doing that. Seth is the one researching the suppliers "with the help of" Claude. Seth is presumably the one deciding when to prompt Claude to make decisions about if they should plant in Iowa in how many days. I think I could also grow corn if someone came and asked me well defined questions and then acted on what I said. I might even be better at it because unlike a Claude output I will still be conscious in 30 seconds.

That is a far cry from sitting down at a command like and saying "Do everything necessary to grow 500 bushels of corn by October".