I know these are generally fake, but they always grind my gears a bit. Literally just screenshot the full message with the “not delivered” part and resend the screenshot until it goes through.
The cause of this for SMS is not the phone, but the network, and the underlying technology. SMS is push-based, compared to Internet messaging which is pull-based, and uses a backoff-based redelivery mechanism. Once your message is sent and has been received by your carrier, deliver is attempted, but if the recipient handset is unavailable the carrier will try periodically to redeliver, and if it still fails the wait period between delivery attempts will increase the longer the recipient is unavailable. May be every five minutes for the first hour, but then once an hour for the next 24, for example.
Each message is its own distinct entity which is treated separately for delivery, just like letters in the post. That’s why it was possible to get this sort of odd-seeming scenario where you have a newer message that made it through, while an older one is still stuck in retry somewhere.
The issue most likely seemed to me to be just that plus the fact that the google service would never retry on SMS when switched back to SMS. So your message wouldn’t be sent until the recipient had a WiFi connection. Ridiculous implementation.
I know these are generally fake, but they always grind my gears a bit. Literally just screenshot the full message with the “not delivered” part and resend the screenshot until it goes through.
I mean what would make even more sense would be to not split up the message so randomly, but then again that would spoil the joke
SMS has a character limit, although most modern phones that still use SMS will at least give you a 3/3 thing and send all three texts at once.
The limit was 140 characters which is also the reason why twitter originally had a 140 character limit: you were able to tweet by SMS
Had some android phones that wouldn’t even notify you if your message didn’t send for like 45 minutes.
Kinda interesting to hear about this stuff as someone who grew up when everyone was already on WhatsApp (at least here in Germany)
The cause of this for SMS is not the phone, but the network, and the underlying technology. SMS is push-based, compared to Internet messaging which is pull-based, and uses a backoff-based redelivery mechanism. Once your message is sent and has been received by your carrier, deliver is attempted, but if the recipient handset is unavailable the carrier will try periodically to redeliver, and if it still fails the wait period between delivery attempts will increase the longer the recipient is unavailable. May be every five minutes for the first hour, but then once an hour for the next 24, for example.
Each message is its own distinct entity which is treated separately for delivery, just like letters in the post. That’s why it was possible to get this sort of odd-seeming scenario where you have a newer message that made it through, while an older one is still stuck in retry somewhere.
Makes sense. I think it’s similar to how email works, right?
Email has bits of both in the chain.
Using the olden-days of desktop email apps as an example then:
The issue most likely seemed to me to be just that plus the fact that the google service would never retry on SMS when switched back to SMS. So your message wouldn’t be sent until the recipient had a WiFi connection. Ridiculous implementation.
But that‘s literally what this is: A screenshot. What you are describing might be exactly how it transpired.
this guy gets jokes
deleted by creator