Live data from Hacker News

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

blog.benjaminste.in

151–160 of 237 posts

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

#151

Earlier quoted context omitted.

I don't know that RyanZAG is so much being user-hostile as reminding us that there are facts of non-free systems that are going translate to user-hostile for at least some subset of users. There's incentives for people who make closed systems to make the most common edges of them comfortable. There's also incentives for them to ignore other sharp edges or to even actively make other edges nearly untraversable.

I came here to say exactly this. Source: I work in the guts of some of the biggest telecom networks on the planet. Federation is a problem because none of the standards interop. The closest thing we had was XMPP which became mega-bloatware as time went by and is now just not something anyone wants to implement (and it's becoming less of an issue as most of the players move away from open-ness). While the technical am…

It's almost absurd the lack of fanfare surrounding AT&Ts proposed phase out of the PSTN in favor of IP networks.

We got number portability and wireless number portability, but the carriers still act as if they own our e.164 addresses and make the transfers arbitrarily difficult. We use phone numbers of SMS, but really we use individual address books, stored in devices, or synchronized with central repositories. We use names to identify people and have to work hard to ensure that our address books are not filled up with duplicates created because we used a one-off email address, or phone number and the phone wasn't able to merge it with an existing contact automatically. We have identity providers that can only represent a small portion of our identity, real names on Facebook and Google+, but cannot resolve that back to our phone numbers or find the best way to contact us at any given time. Presence, which was the real promise of IM and XMPP (and SIMPLE if you must) is not integrated. I cannot determine before hand whether somebody is available to talk on the phone, would prefer a text message, or if I should leave a push voice message they can listen to at their leisure.

Even calling a company with a well designed IVR is still a confusing waste of time, when the device I am calling that system from is smart enough to contain any identifier or proof of identity that the called party would need, the protocols are artificially limited to phone numbers as identifiers. There is also no out of band solution to this problem, or the the problem of selecting what department I would prefer to speak with about a problem without navigating a menu that the interface on my device is not really designed to use. Think DTMF on an Android device where the screen shuts off.

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

#153
post #65

Same problem here and I know quite a few people who've had these issues as well. iMessage is a huge mess - even if you're still using your iPhone. Back in December, when I was still on iPhone, I went in a month-long trip abroad. Since data roaming still costs a fortune, I had data switched off most of the time. I'd just connect on wifi whenever possible and occasionally switched on the data connection when I really n…

I had exactly the same issue on holiday last year. When out and about I wouldn't see any messages and then as soon as I got back to wifi they'd all come through.

Just another of the many apple straws that have been breaking the camel's back for me recently. The fact that it could haunt me even after I completely leave their platform is truly disturbing.

I feel that this issue needs a lot of noise. Bug or not it should be filed under non-competitive behaviour.

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

#154

Earlier quoted context omitted.

Hey, this is John Doe, iMessaging you from his email.

Touché. Though I suspect it might be prudent to further explain that that means they need to add your email address to your contact, as their mind will be blown at that point.

...just like they do when the receive a text for the first time.

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

#155
post #120
post #30

Just think, if you hadn't used a proprietary messaging solution as your default contact method, you'd be able to easily control how you receive the messages. Maybe stuff like this happening is a good thing as it drills home the point the 'crazy free software lunatics' have been going on about for some time. Having this kind of thing happen to someone makes the stuff FSF+co says a bit more relevant and ultimately help…

Yeah, other peoples' misfortunes are totally "a good thing" if they help illustrate the motivations for one's own political agenda.

If other peoples' misfortunes are influential in keeping others from making bad decisions that have an effect on us all, then yes.

Even the 'good' behavior in this case is awful. Why would a text message fallback to MMS rather than SMS? I'm pretty sure it's because Apple wants non-iPhone users to think of their phones as broken.

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

#156
post #25
post #6

Earlier quoted context omitted.

This is a such wrong reply. The OP did not complain about his message history, he was talking about message histories of all his friends and relatives. Do you really think it could be socially acceptable to approach each of your friends and relative and tell them: "If message histories are your only copy of family/friends photos, you're doing it wrong." ?

I don't even think it is acceptable to approach each of your friends and relatives and pester them with some technical issue that shouldn't exist in the first place. The proposed fix just isn't a viable solution.

This is true, but on the flipside it's hardly Apple's fault if the only copy they have of highly important and sentimental photos is a cached messaging stream. There are countless ways to back up that data. It's like blaming Microsoft because you didn't save transferred files during a Skype session. Once they're on you're end, they're your problem. Apple's job is to send them and make sure they arrive, that's it.

This bug sucks and Apple's solution isn't a good one, but that rebuttal is equally weak. Use PhoneDisk, PhoneView or one of the other methods to pull a text messaging history if it's that important to you and then blow it away.

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

#158
post #50

Earlier quoted context omitted.

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

Email? Really, now that everyone has email on their phones, why bother with SMS or these SMS-like systems? Email is more reliable, more flexible, and seems to be just as fast in practice.

Except there is no email app that I know of that presents conversations in way that is as easily readable as line, messenger, etc. I wouldn't want that either as the current presentation is perfect for large amounts of information that I get in my other emails.

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

#159
post #112

A fairly simple solution would be to get a Google Voice number, that would forward to your real number - and have people text you via Google Voice. However, if anybody calls (or sends an old-style SMS to) your old number, it would still come through.

Google Voice has its own issues. He can't group message (with MMS) with Google Voice. Worse.. it fails silently.
Post reply on HN