Re:iMessage Should Have a Dead Battery Auto-Responder
by hartleybrody on Sunday February 24, 2013 @03:30PM
(#5275768)
Agreed. Whether it's "I don't have service" or "My battery is dead," there are a number of conditions that keep a recipient from seeing a message right away, all of which are (usually) temporary.
Relying on "delivered" takes care of all of those situations, and is much more elegant in the UI than adding an "auto responder" message.
Re:iMessage Should Have a Dead Battery Auto-Responder
by gpmcadam on Sunday February 24, 2013 @03:45PM
(#5275820)
Does 'Delivered' show up when the message is received by another iOS device? e.g. I often leave my iPad at home but still connected to iMessage, and if that receives the messages my iPhone doesn't, wouldn't this give a false impression of delivery to the sender?
Re:iMessage Should Have a Dead Battery Auto-Responder
by josho on Sunday February 24, 2013 @03:59PM
(#5275889)
iMessage's are sent to all of your devices. I have iMessage on my mac, iPhone & iPad. All 3 devices receive messages sent to me. That's true even if one of the device is turned off for some period of time. Apple, did seem to go through some growing pains where this didn't always work as above.
To answer your other question the delivered flag is set if any of your devices receives the message.
Re:iMessage Should Have a Dead Battery Auto-Responder
by matthew-wegner on Sunday February 24, 2013 @04:06PM
(#5275916)
iMessage gets tricky when you have multiple devices.
For example, I went out of the country, but left my iPad at home (which also receives iMessages to my phone #). Because my phone wasn't data roaming, and my iPad was still on the network at home, iMessages were being delivered to the iPad. It basically meant anyone with an iPhone couldn't text me, because the text message fallback wasn't triggering. I had to find wifi with my iPhone to catch up on texts.
The "dead battery" auto-responder has the same issue. What if my iPhone battery is dead, but I'm on a Mountain Lion MacBook and getting messages there?
Re:iMessage Should Have a Dead Battery Auto-Responder
by whalesalad on Sunday February 24, 2013 @03:04PM
(#5275679)
It's really unreliable and half assed. The parent commenter is a absolutely right. iMessage is full of bugs they need to really fix them! They have done an amazing thing though.
Sidenote: apple has the ability to mine so many conversations for data. It's more intimate than twitter and I'd imagine more iMessages are sent each day than tweets. If something happens anywhere in the world Apple would theoretically be the first to know. Kinda nuts.
Re:iMessage Should Have a Dead Battery Auto-Responder
by zapu on Sunday February 24, 2013 @03:20PM
(#5275735)
I wasn't aware how buggy Messages application can be until I started using it more. Weird UI glitches, messages coming out of order (?) are the two I notice often.
Re:iMessage Should Have a Dead Battery Auto-Responder
by nwh on Sunday February 24, 2013 @03:03PM
(#5275675)
On both systems, you can't do anything but search for the first instance of a message. It is completely and utterly useless. It also hangs and and crashes on my system if you try.
ED: I tried searching for a word in Messages at five minutes ago, and the results still haven't appeared. 100% CPU usage.
ED2: 10 minutes now, 2.24GB of memory use.
ED3: Results showed, then client crashed at 13 minutes.
Re:iMessage Should Have a Dead Battery Auto-Responder
by almostbutnot on Sunday February 24, 2013 @02:41PM
(#5275585)
There are privacy concerns when you tell people about the state of another persons device. There is also the concept of sending a message saying a devices battery is dead "gosh iPhones always have dead batteries I keep getting this alert from my friends". These are good intention designs but not quite there.
Re:iMessage Should Have a Dead Battery Auto-Responder
by rem1313 on Sunday February 24, 2013 @02:46PM
(#5275618)
iMessages has built in notification to the sender if the message has been delivered to the receiver, hence the status "Delivered" or (if receiver has opted-in) also Read status. I see no point in this feature, since the phone could be dead for various reasons, not just battery
Re:iMessage Should Have a Dead Battery Auto-Responder
by k33l0r on Sunday February 24, 2013 @03:13PM
(#5275716)
It would be nice if the delivered indicator could be relied upon, but it seems to report that a message has been delivered once the Apple servers have received it, not when the destination device has received it.
This is especially noticeable under poor network conditions (I think I first noticed it at a music festival where even regular SMS messages struggled to get through due to network congestion).
Re:iMessage Should Have a Dead Battery Auto-Responder
by Terretta on Monday February 25, 2013 @12:08AM
(#5277407)
Nope. It needs to hit a device to say Delivered.
For example, if the recipient is out of 3G data coverage but can fall back to SMS, you won't get Delivered, you'll get a line across your conversation denoting a switch to Text Message and a different color bubble.
(Several people I message are in marginal coverage areas several hours a day, so I get to see this in action daily.)
Re:iMessage Should Have a Dead Battery Auto-Responder
by andrewroycarter on Sunday February 24, 2013 @06:26PM
(#5276432)
This doesn't make any sense at all. iMessage is now tied to my iPhone, my iPad, an iPod Touch, two iMacs, and a Macbook Air. If my iPhone's battery dies, how will Apple know that I'm not in front of another device capable of getting messages?
"One potential reason that Apple wouldn’t implement this feature is that it increases user awareness of dead iPhone batteries"
I don't even
Re:iMessage Should Have a Dead Battery Auto-Responder
by Pwnadog on Sunday February 24, 2013 @02:38PM
(#5275567)
Why not turn it around and have iMessages send a "message received" notification when receiving a message?
Have it display like a little checkmark next to any sent message that turns green if the other phone pings back.
Just that - no read receipt like there is now, as that isn't always convenient.
Re:iMessage Should Have a Dead Battery Auto-Responder
by treblig on Sunday February 24, 2013 @02:38PM
(#5275566)
Yep, it is built in, but many (including myself) disable it. It's pretty common that I accidentally open a message, but I don't have a response / a chance to respond yet, and I don't want the person to think I'm ignoring them.
Re:iMessage Should Have a Dead Battery Auto-Responder
by keeperofdakeys on Sunday February 24, 2013 @03:20PM
(#5275733)
In fact, SMS already has this system in place. Naturally there are some networks/phones that don't support it, and its meaning can vary from "network received" to "phone received".
Re:iMessage Should Have a Dead Battery Auto-Responder
by SparksZilla on Sunday February 24, 2013 @02:17PM
(#5275475)
I like this, but can see some problems with iMessage on multiple devices. Ignoring that, I'd love to get a push notification at ~5% battery asking me if I'd like to put an auto-responder on.
Re:iMessage Should Have a Dead Battery Auto-Responder
by thegrul on Sunday February 24, 2013 @02:33PM
(#5275539)
It can't make any negative remarks about the battery life of any idevice, but it could be kinda nice if it said whether or not the receivers idevice is turned off.
Re:iMessage Should Have a Dead Battery Auto-Responder
by m_eiman on Sunday February 24, 2013 @03:53PM
(#5275859)
The problem hasn't got anything to do with delivery notifications or auto-responders: if you need an answer right away you must use a synchronous form of communication, e.g. voice call.
iMessage, SMS, email et al are async by design. Until you hear or see an ack that's from the actual recipient (and not something automated by a device), you can't be sure the message has been properly received.
Re:iMessage Should Have a Dead Battery Auto-Responder
by m_eiman on Monday February 25, 2013 @11:30AM
(#5279725)
Yes, but that doesn't mean the recipient actually read it - it means that iMessage is/has been the active application on at least one of the recipient's devices.
But it can be spotty at times with poor data connection.
Relying on "delivered" takes care of all of those situations, and is much more elegant in the UI than adding an "auto responder" message.
To answer your other question the delivered flag is set if any of your devices receives the message.
For example, I went out of the country, but left my iPad at home (which also receives iMessages to my phone #). Because my phone wasn't data roaming, and my iPad was still on the network at home, iMessages were being delivered to the iPad. It basically meant anyone with an iPhone couldn't text me, because the text message fallback wasn't triggering. I had to find wifi with my iPhone to catch up on texts.
The "dead battery" auto-responder has the same issue. What if my iPhone battery is dead, but I'm on a Mountain Lion MacBook and getting messages there?
Message search is also built into the iOS spotlight screen (left of first home screen).
Sidenote: apple has the ability to mine so many conversations for data. It's more intimate than twitter and I'd imagine more iMessages are sent each day than tweets. If something happens anywhere in the world Apple would theoretically be the first to know. Kinda nuts.
ED: I tried searching for a word in Messages at five minutes ago, and the results still haven't appeared. 100% CPU usage.
ED2: 10 minutes now, 2.24GB of memory use.
ED3: Results showed, then client crashed at 13 minutes.
This is especially noticeable under poor network conditions (I think I first noticed it at a music festival where even regular SMS messages struggled to get through due to network congestion).
For example, if the recipient is out of 3G data coverage but can fall back to SMS, you won't get Delivered, you'll get a line across your conversation denoting a switch to Text Message and a different color bubble.
(Several people I message are in marginal coverage areas several hours a day, so I get to see this in action daily.)
"One potential reason that Apple wouldn’t implement this feature is that it increases user awareness of dead iPhone batteries" I don't even
iMessage, SMS, email et al are async by design. Until you hear or see an ack that's from the actual recipient (and not something automated by a device), you can't be sure the message has been properly received.