4 ms·
Not to be conspiratorial but I find all of this to be pretty intentional. It's currently very hard for me to stay on T-Mobile's legacy (i.e. true) PAYG plan whi
by lagg 7y ago
Not to be conspiratorial but I find all of this to be pretty intentional. It's currently very hard for me to stay on T-Mobile's legacy (i.e. true) PAYG plan which only supports regular texts. I often have to ask people I'm doing business with to send things as a regular text because emojis and pics don't download.
Looking at the overview on wikipedia and gsma, this thing is feature creeped to the absolute rim before overflowing. Including parts of the specification for APIs and app integration if I'm reading it correctly.
Frankly, if a corporation wanted to lay the groundwork for itself to be the private contractor for when the government wants to make use of the data that can be hoovered from these open channels. It would look a hell of a lot like Google. All this feature creep in abundance is a great way to lock people into centralized monolithic apps or force them into new revenue streams (again, they're already trying it with my PAYG plan for MMS).
I could take it to its greatest logical conclusion especially considering the API, app integration & visible protocol fingerprint and just say this is a great way to introduce WeChat by Google.
I hope this doesn't sound irrational. But I for one find it irrational that I'm even in this position with regular texting versus MMS. It's like phone carriers are the only ones allowed to have shitty interoperability of this kind. Getting really tired of it. Also I hope you're right that their fuckups are resulting in lower adoption, because 68 (including T-Mobile) carriers have already signed onto the Universal Profile part of the spec:
https://en.wikipedia.org/wiki/Rich_Communication_Services#Status https://en.wikipedia.org/wiki/Rich_Communication_Services#St...