And make it melanine tested
I have converted some tuya bulbs in the past, but its never been a good time. The exploit methods tend to get patched, so I had to open the bulbs and solder wires to flash, and the bulbs don't go back together nicely. Better to just avoid that headache imo.
Yeah, there would be a lot of potential for leaks, but if they are one-time-codes that wouldn't be too bad.
Esphome or ZigBee bulbs are the way to go, avoid tuya for WiFi bulbs
https://www.athom.tech/esphome
ZigBee bulbs I have gotten from aliexpress, they are usually pretty good, but you'll need a ZigBee antenna or bridge.
Tuya require a cloud connection, so best to avoid.
Your website is dead.
If the merchant is hoarding the data, they want to do it. If they want to do it, why would they use your framework?
Also, merchants need your name and address to ship the product to you...
Sure, you might today, but tomorrow? How can anyone trust that you wont start serving malicious links?
Better is a wild claim.
You're right, gists do seem to update with the static url, however that isnt necessarily better, it now means your gist is effectively under your control, and you can replace the installers with malware packed ones. Operating a software repository/installer requires that people trust you, and that is basically impossible for a no-name dev with no history.
You ideally should be doing checksum checks as well.
Solar, battery, EV, make sure your appliances are efficient and electric, pay for green energy. Encourage your neighbours to do the same.
Other than that, brace for impact. Seek out a local "climate cafe", they likely have resources to help:
Some feedback:
let remote_url = "https://gist.githubusercontent.com/ZeSystem-Inc/20ddc1ac41d73c6033cee3b4a5ab1a85/raw";
You have effectively hardcoded the list of software you support, ideally you should be able to dynamically update the list, otherwise you have no way to revoke or update versions if required. And if its hardcoded, why bother network requesting for it, just build it into the binary. Would be a little larger binary, but even faster.
No dependency resolution – eliminates fragility.
Meaningless, there is no dependency resolution because thats done for you by the installers.
Written in Rust – memory-safe, zero-cost, ultra-fast.
The task you are doing is entirely IO bound, rusts performance is irrelevant.
KYC is not just for funsies, they are legal requirements for a lot of businesses. If they don't legally have to store information, they can just choose not to. It doesnt require a framework, Lemmy manages just fine without storing personal data.
I agree in general, but not every country has a simple and easy licencing system. And if your just acquiring radios for shit-hits-the-fan scenarios, rather than regular use, expending the effort for a licence doesnt make sense to me.
In Aus, its a multiday in person class, with exams at fixed times during the year. And I've seen the course work, its mindnumbingly easy, it should be an online multiple choice. I would do it in a heartbeat if it were online.