2026-10-24 22:22 UTC
@violet@estradiol.city @Farbs@mastodon.social The browser vendors came up with "WebRTC". This was a complex bundle of technologies for in-browser teleconferencing and it is the basis of any calls you make in the browser today. Part of the WebRTC stack was a high-quality set of P2P primitives, allowing browser tabs to talk to browser tabs.
And then they realized "oh shit… P2P is kinda unsafe though. If we add this, we need to add a permission". And browser vendors *hate* adding permissions. And P2P is hard to describe.
Replies (1)
-
@mcc@mastodon.social 2026-10-24 22:24
@violet@estradiol.city @Farbs@mastodon.social So they decided to make the P2P permission, inscrutably, *be* the microphone permission. If you get microphone permissions you can P2P, and if you don't you cannot. Which broadly means that if you are a gamedev like me and Farbs, you go "omg! P2P! I can use this for games!" and then realize we have to ask for microphone permission, which is super sketchy and hard to explain to our users. And then gamedevs just don't use WebRTC, which is probably what the browser devs wanted anyway