What is the problem you're trying to solve? Is twitter... er... I mean X not unreliable enough for you?
Imagine someone depending on a resource that's on a device that moves in and out of service as you lose coverage or have to reboot to get bluetooth pairing to work right.
And what if you wanted to support TLS. Try explaining to normal people why they're getting security warnings because your CARRIER doesn't support dynamic DNS so your cert SN or SAN doesn't match your FQDN.
And proxies. I don't even want to think what carrier data teams will do to proxy requests.
I really like the idea of a carrier / manufacturer neutral protocol to get data (pictures, contact vCard, call logs, music, etc.) on and off a phone.
What is the problem you're trying to solve? Is twitter... er... I mean X not unreliable enough for you?
Imagine someone depending on a resource that's on a device that moves in and out of service as you lose coverage or have to reboot to get bluetooth pairing to work right.
And what if you wanted to support TLS. Try explaining to normal people why they're getting security warnings because your CARRIER doesn't support dynamic DNS so your cert SN or SAN doesn't match your FQDN.
And proxies. I don't even want to think what carrier data teams will do to proxy requests.
I really like the idea of a carrier / manufacturer neutral protocol to get data (pictures, contact vCard, call logs, music, etc.) on and off a phone.
But it's not HTTP(S).