Post B64ELPVLb7BONWYfz6 by tully@cathode.church
 (DIR) More posts by tully@cathode.church
 (DIR) Post #B649g0Mlkzu8ivXy08 by Unixbigot@aus.social
       0 likes, 0 repeats
       
       The fact that only google chrome fully supports web serial and web bluetooth is becoming increasingly stressful to me.Two questions:* What browser would you recommend when you want to do use the web {serial,ble} APIs (eg for flashing or interacting with iot devices) * How do we get Mozilla and/or Apple to support these APIs properly?
       
 (DIR) Post #B649g0Yp2BXtKJBamu by linear@nya.social
       0 likes, 0 repeats
       
       @Unixbigot@aus.social my own personal response has been to angrily rewrite whatever tool requires it, in order to have an actual flashing tool that i can use. especially since even with the browsers that supposedly support it, i have never gotten it to function under Linux anyway, and stopped trying.but i also have the opinion (which i find myself increasingly alone in) that a web browser should not under any circumstances have the permissions to access such devices, and that it is an anti-feature which Google was mistaken in implementing.
       
 (DIR) Post #B64ELPVLb7BONWYfz6 by tully@cathode.church
       0 likes, 0 repeats
       
       @linear @Unixbigot yep, said it better than I ever could
       
 (DIR) Post #B64ELPhkqz6j00MaK8 by Unixbigot@aus.social
       0 likes, 0 repeats
       
       @tully @linear okay, turn the should-browsers-support-hardware-access question around.  How *do* we allow people to be able to connect to and configure IoT devices (say, your solar inverter, or the battery in your e-bike, or your air conditioner) *without* having to force the user to install a single use application for every smart device they own?   (Properly self documenting Bluetooth GATT profiles that supply data type and user description attributes for each characteristic is my best answer so far)
       
 (DIR) Post #B64ELPtS9UStaHpvYe by linear@nya.social
       0 likes, 0 repeats
       
       @Unixbigot@aus.social @tully@cathode.church that's also my best answer so far, and is more in the direction what i've tried to steer embedded projects i've worked on towards (though this exact issue has never come up, similar ones have)