Live data from Hacker News

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

blog.benjaminste.in

171–180 of 237 posts

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

#171
post #52

The saddest part about this story is perhaps the fact that iMessage was supposed to be open and allow other phone builders to use it. Having it truly cross-platform in the first place would have avoided a situation like this :(

Source? I have never heard anything about it being 'open', or even planned to be.

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

#172
post #50

Earlier quoted context omitted.

So, what's an open-source alternative to iMessage that lots of people use?

The best alternative is TextSecure[0] I think (another one is the Telegram[1]), but they are not used by "lots of people". [0] - https://whispersystems.org/ [1] - https://telegram.org/

Yes, for the love of god please use textsecure. Unfortunately it's android only at the moment.

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

#173
post #12
post #5

I know it's annoying but the best solution here just seems to change your number. Don't lose your mind over this one. edit : seems like people don't understand my post. If you have a voice, the good thing to do is to make a blog post and submit it to websites like HN. The guy did it, now what can he do if he needs a quick fix? If he's in rush? Change number. It's really not that terrible and I do it every year withou…

What happens to the next person who gets that number?

The problem is not server-side but on the client. So as baby said, it won't be an issue if the next person doesn't have the same people to message.

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

#174

This has been happening for over 2 years now. I've met multiple people in real life (including total non-techies) that have run into this. It's more common than you'd think. Basically anyone moving from an iPhone to Android (or any other phone I assume) will have this problem. At this point, it's obvious Apple is ok with this. It's a giant "fuck you" to anyone moving away from them and it leaves a bad taste in your m…

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.

> there's simply no good incentive for them to prioritize fixing this

There's plenty of incentive for them to fix this. OP is far from the only one calling Apple customer support or going to a Genius bar over this issue. Those costs add up, unless they're also considering the incentives on the other side of the ledger.

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

#176
post #129
post #91

Earlier quoted context omitted.

Um. I'm not the one who made iMessage - you need to look at the guys making locked down messaging systems for the user-hostile actions causing problems like these and no doubt much more in the future. If I could help these people out and give them a script to run to fix their problem I would - but of course I can't, because everything is locked down by others who are putting their own vendor lock-in above user satisf…

You don't do a good job of envangelising for open source and open standards by making posts like the 2 in this thread.

[deleted]

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

#177
post #129
post #91

Earlier quoted context omitted.

Um. I'm not the one who made iMessage - you need to look at the guys making locked down messaging systems for the user-hostile actions causing problems like these and no doubt much more in the future. If I could help these people out and give them a script to run to fix their problem I would - but of course I can't, because everything is locked down by others who are putting their own vendor lock-in above user satisf…

You don't do a good job of envangelising for open source and open standards by making posts like the 2 in this thread.

I disagree, I think he made excellent points, and I fail to see why you think there is a problem with his comments.

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

#179

This has been happening for over 2 years now. I've met multiple people in real life (including total non-techies) that have run into this. It's more common than you'd think. Basically anyone moving from an iPhone to Android (or any other phone I assume) will have this problem. At this point, it's obvious Apple is ok with this. It's a giant "fuck you" to anyone moving away from them and it leaves a bad taste in your m…

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.

Fixing it is the right thing to do. They're seriously screwing with people's communications otherwise. If you're saying that they're avoiding the right thing because it's too hard and there's no incentive, then to me that is essentially saying that they are doing it on purpose.

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

#180
I recently made exactly ths same switch, and unsurprisingly had exactly this issue. I resolved it by turning on my iPhone, putting it in airplane mode, and turning on wireless.

I then went into Settings >> Messages and turned off iMessage. All the iPhones that had previously been trying to send me messages via iMessage then started routing messages to me via text.

Post reply on HN