TextNow currently uses GCM for push notifications. In theory, we could work around this. Once we get #6, we can theoretically negotiate for a GCM token via TextNowPlus, then send only that token to an external MQTT, an open push messenging protocol. So now, that server is acting on my behalf, getting the GCM push notifications, and then sending a non-google one to my phone. The server only knows timing, but doesn't get access to the message (as I understand it), and so others could kinda trust it too.
And obviously, the big hooray here is that we have a path toward a solution for getting "normal" voice/SMS usage on a totally wifi device, with no Google Framework stuff, and with silent upgrade to encryption via TextSecure/Redphone! :)
patcon
commented
9 years ago
TextNow currently uses GCM for push notifications. In theory, we could work around this. Once we get #6, we can theoretically negotiate for a GCM token via TextNowPlus, then send only that token to an external MQTT, an open push messenging protocol. So now, that server is acting on my behalf, getting the GCM push notifications, and then sending a non-google one to my phone. The server only knows timing, but doesn't get access to the message (as I understand it), and so others could kinda trust it too.
And obviously, the big hooray here is that we have a path toward a solution for getting "normal" voice/SMS usage on a totally wifi device, with no Google Framework stuff, and with silent upgrade to encryption via TextSecure/Redphone! :)