On 10 Feb 2015, at 7:44 pm, Wilson Page <[email protected]> wrote:

> Regarding access to telephony. We hoped that fxos would get to the point 
> where it is so hackable that users could potentially replace the dialer app 
> with something third-party. It's a bold move, but it's proof we've succeeded 
> in making 'the phone for makers’.

Makers can already replace the dialer app via sideloading - have we succeeded? 
Flippancy aside, would a replaceable dialer be contingent on being a 
replacement dialer being dynamic hosted code or could it maybe be packaged? 

But as I say, if there is a strong use case for telephony, then lets start 
discussing how we might either alter or create a new telephony that mitigates 
the risks. To be honest I’m unclear how we can make telephony safe enough for 
websites. I’ve created an etherpad here to dive deeper into the API and look at 
the specific risks. 

https://etherpad.mozilla.org/grantwebtelephony

Thanks,
Paul
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to