Like I get it, they don’t want someone torrenting 100tb of data in a day. That bogs things down.

No, that isn’t accurate and isn’t getting it.

All the data caps today are for total cumulative quantity per billing cycle. That is not a reliable method for controlling what actually bogs things down, which is the bandwidth used at any moment (speed).

Limiting bandwidth is also done by most ISPs today, but that’s not what this is asking to change. The data caps are exclusively a way to charge more.

Shouldn’t the pipeline have failed unless the functional tests passed?

One way would be by implementing features the Lemmy devs have no interest in such as better interoperability with other fediverse platforms. If any added feature turns out to be well received and in demand, it would pressure the others to implement similar.

That way, you don’t need to connect them to the manufacturer’s (probably insecure) cloud.

The problem is that these projects do connect to the manufacturer’s cloud.

I agree that the company is handling this the wrong way, but it is possible for 3rd-party code to negatively impact the service for other users. The right way to address any legitimate issues would be to have reasonable rate limits and work with the developer to fix any concerns.

This is also why I believe in choosing devices with local control instead of those which require cloud services. For example, Louis’ video mentions air conditioners. Get one that can use a wired thermostat that you control over Z-Wave or ZigBee.

You can sanitize at boiling, and far below that too. For actual sterilization, you’d need to be above boiling using something like an autoclave or pressure cooker.

Some dishwashers do get hot enough, having options specifically for sanitizing during a cycle. It’s essentially Pasteurization which factors in not just temperature, but also time. While flash Pasteurization requires high temperature, longer times at lower temperatures can effectively kill harmful microorganisms.