Post #2246211
2026-05-07 07:47 UTC
@jaffathecake@mastodon.social @ash@icosahedron.website So the API itself doesn't need any ToS, at least not in other browsers. That's a Chrome product attribute that lots of folks will object to, but it's not part of the API any more than Web MIDI requiring an extension in FF is.
The deeper problem is model interoperability. No idea how we'll get close to that with an API that has no way to specify model or version.
Replies (1)
-
@jaffathecake@mastodon.social 2026-05-07 07:58
@slightlyoff@toot.cafe I think you're underestimating the ToS issue. See the problem I laid out here https://github.com/mozilla/standards-positions/issues/1213#issuecomment-4347988313. If we allow APIs to have ToS, it creates an environment where developers are encouraged to block usage in other browsers in case they release with a ToS that'll get them sued.