lol you really haven’t got a clue based on that comment. I’d love to see how telegram (scammers heaven and way to easy to impersonate someone else) can deal with emergency situations. Let alone fall back to sms.
What do you do when your app doesn’t work? What are the layers ensuring it does work? How does that app ensure it arrives to everyone?
Out of interest, what part of it broke? My lightning cables would always die at the point where the cable met the lightning connector end.
What do you do with your cords? I've got a Macbook Pro that I bought in 2019 that still uses its usb-c cord, and my daughter is using that one. Same as my current one that I use daily to plug in with my hub and screen.
yep you just said it yourself you don't understand anything probably an american who doesn't know better and didn't even read the post correctly.
Ah, sorry, didn't see this message before I commented. I think perhaps you've just been unlucky- in years of using USB C cables none of mine have broken, but they haven't taken the pounding the lightning cables took that broke. I've usually gone through one lightning cable a year- I found the Amazon ones lasted a bit longer than the Apple ones.
??? Did I? That is a bit rude towards `americans`, and no, definitely not. Just someone from an entirely different continent who is actually involved with interoperability standards through ISO, ETSI and IEC.
Awesome, well, if it is so simple and robust it makes one wonder what the issue is: Doesn't it? Let's get rid of all the other layers, services, integrations, fallback mechanisms, and a whole raft of specifications and standards to make this work under all circumstances. It's just TPC/IP init
TCP/IP is the backbone and standard of all Internet network transmissions. The beauty of it is that dozens of fallback specifications have been built around it because of how widespread it is. There is a strong commercial interest in keeping any service running with high uptime over TCP/IP because of its ubiquity.Awesome, well, if it is so simple and robust it makes one wonder what the issue is: Doesn't it? Let's get rid of all the other layers, services, integrations, fallback mechanisms, and a whole raft of specifications and standards to make this work under all circumstances. It's just TPC/IP init
You're right. It's not difficult if you bother to read. The poster said it benefits BOTH sides. Try to keep up
That’s funny because they have started adopting RCS in the UK by at least 2 major carriers.
Google Jibe is already used by other UK mobile networks and the reason we’re doing this is because Google have plans for their RCS service to make it even better than it is currently, and with all UK networks using a single shared platform, the service can be developed at speed which will give customers a better service, sooner. We’re unable to do the same thing with our own RCS platform and so this is an easy decision for us as it’ll result in a better experience for our RCS users in the future.
oh you mean where it says they use GOOGLE to do it its not native, carriers don't want to spend money thats why it was abandoned in the first place 🤦♂️
That’s what I said originally carriers where using RCS
It’s not tribal, most of us prefer iMessage to janky 3rd party apps
