Re: [w3ctag/design-reviews] On-device Web Speech API (Issue #1038)

jyasskin left a comment (w3ctag/design-reviews#1038)

Thanks; I think we have almost enough to re-discuss this. My last remaining questions are:

1. What's one concrete website that might adopt this API only if it provides the mechanism to guarantee that audio is not sent across the network, even encrypted to another device controlled by the user? Have they described their requirement in public in a place the TAG could read?
2. What's one website that needs to recognize audio on the receiver side, and can you point us to a place where they've documented how this architecture is better for their users than either having senders recognize the audio or having the cloud server recognize it?

It would be great if the agreed changes and the concrete use cases for parts of the current design that the TAG (or others) were concerned, could be reflected in the explainer, asap.

Thanks.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1038#issuecomment-2835802917
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1038/2835802917@github.com>