Hacker News Reader

From a security perspective you should consider what users are already doing and if introducing a feature can be better security than that.

Users are already installing local applications from untrustworthy hardware vendors just to interact with bluetooth devices. I think a web bluetooth standard is an improvement on that.

Flip side-- just keep adding features until your userbase is large enough to justify a security team that a) assumes the API is a giant dumpster fire and b) redesigns the system so that it continues to work even when lots of things are burning.

Commonly known as The Principle of Least Power.