On 20/03/2013, at 14:40, Vicamo Yang wrote: > 1) You can send/receive binary SMS if you want. Sending takes additional > works to be done, but is minor. Binary SMS messages will neither trigger > notifications to the user, nor be stored in database. At least for now. > Sounds more silent, doesn't it? >
That sounds interesting. Do we already support sending binary SMS? I'll need to check with Telefónica guys (probably David knows about this) if the flow is possible with binary SMS. > 2) You don't really need a "SMS" permission, just build the API in > mozPay and makes requests to SmsService to send the message for you. Yes. I was talking about an explicit permission to let the user know that the payment provider is requesting the send of an SMS. If I am not wrong, explicit permissions triggers a system dialog to allow the user choose to allow or forbid the use of certain APIs. Is a privacy and transparency measure more than a security one in this case. In the end, the payment flow is trusted. I commented about the explicit permission cause we already have a history of previous concerns about user's privacy in the payment flow. > 3) Do users pay for these slient SMS messages? I guess that depends on the operator. But I've been told that for Telefonica this short code would be free of charge. > 4) Take Line, a popular messaging app from Japan, for example. The app > listens incoming SMS for a certain period, waiting for one that matches > some criteria, paste message text to the authentication form, and delete > that SMS when everything is done. Isn't that silent enough for us? If I am not wrong, with the current implementation of the SMS API that flow would trigger an incoming SMS notification and will store the SMS in the database. That works for me, but is more a product call to decide if we want to completely silence the SMS flow or is good enough to let the notification about an SMS reception appear and then delete that SMS from the database. Thanks Vicamo! Cheers, / Fernando _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
