Live data from Hacker News

iOS holding my phone number hostage = the worst bug I’ve ever experienced

blog.benjaminste.in

201–210 of 237 posts

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#201
post #134

Earlier quoted context omitted.

SMS is also a proprietary solution, as far as I know. If you don't think so, check the costs of integrating with SMS...

SMS is interoperable between every phone and phone company on the planet.

Try switching companies and see how well it works. I have no idea what the actual porting process involves, but then neither did the 2 big telecoms I was dealing with. I had weeks of carrying 2 phones. One received calls, the other SMS. And the telecoms sat there blaming each other. Vodafone and Telecom. New Zealand.

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#204

Earlier quoted context omitted.

That's incredibly presumptuous of you to claim Apple is doing this purposely. It seems pretty obvious to me that it's a non-trivial fix for Apple, and that there's simply no good incentive for them to prioritize fixing this over the myriad other things their engineers could be spending their time on.

Apparently it doesn't have much priority on their list considering the problem has been around for two years. If you think about how fast the mobile landscape has changed, this is no excuse for Apple

2 years? 2 years is nothing. There are thousands upon thousands of open bug repots on Apple products older than 2 years.

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#206

This is the problem with bolting proprietary standards on top of legacy methodology. I do swear that iOS by default does send SMS after 5 minutes if it can't do it over iMessage though?

Not always, even when 'send as SMS when iMessage is unavailable' is turned on. Fixing iMessage issues is near impossible due to the complete absence of useful settings.

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#207

I had this same problem and the best case fix seems to be to reset your Apple ID password; this forces you to log out from all devices, and so iMessage will at least error out for people who try and text you. But their devices will never go back to normal texts unless they specifically force it too, and that kind of lock-in is utter bullshit.

Nice fix. I hate changing this password as the everything needs updating. Appletv, App Store (on 3 macs iphone and iPad) iTunes (2 macs iphone and iPad for music) home sharing (on everything) iMessage (Mac and iphone), FaceTime (Mac, iphone, iPad), developer portal (Mac), itunes connect (Mac), email (Mac, iphone, iPad) and iCloud backups on everything. It is hellish and invariably something is missed so the bugs aren't ironed out for weeks. Don't change your passwords as Appleland becomes a dark and hellish place.

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#208
>But to ask my wife, my sister, my best friends, and literally every person I know to delete THEIR message histories? You’ve got to be kidding me!

That is true, but not because of photos - don't they keep backups?

I guess this is why not to use vendor lock-in software instead of a globally accepted standard for basic communication.

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#210
post #134

Earlier quoted context omitted.

SMS is interoperable between every phone and phone company on the planet.

Try switching companies and see how well it works. I have no idea what the actual porting process involves, but then neither did the 2 big telecoms I was dealing with. I had weeks of carrying 2 phones. One received calls, the other SMS. And the telecoms sat there blaming each other. Vodafone and Telecom. New Zealand.

Sounds like carriers there are incompetent then.

When I (UK) switched in the late 2000s, it took about an hour.

Post reply on HN