Arcka
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.
airbags are single-use. […] If you test it to confirm you lost the air bag
Please try to avoid presenting your hypothesis as fact. If your third sentence was phrased as a question it’d be fine. Currently it’s misinformation.
Of course it can be tested without destroying it. The actual air bag component could be disconnected from the rest of the device and the connection point monitored for the appropriate voltage/current required for activation.
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.
Ummm
This is the equivalent of saying that MS Outlook is a community. It’s not and neither is Lemmy. Each server has its own rules, and each community on those servers can add rules beyond that.
Address a specific community or server, there’s no central control over the fediverse.