Why is it so hard to hold back moans?

Question

Beeline

This SMS was sent:



But this is received:



How can this be explained? What kind of failure in the work of the beeline (both numbers are beeline)?

UPD1: the version of the problem with gluing different parts of the SMS looks very likely. The question remains with where the second part of the glued SMS comes from: from the sender's device, from the recipient's device, or from the third device. The version that the glued part is taken from the device of the sender or the recipient looks more likely, but such parts were not found on both devices (or they are not recognized as such). So, two working versions:
1. A part of the SMS previously sent or received by the sender or recipient has stuck, but they do not admit it.
2. A part of the SMS that belongs to neither the sender nor the recipient has stuck. In this case, the beeline is “guilty”. I would like to hear the opinion of experts: what is the probability of such a collision?

UPD2: intrigue number 1 is revealed: such an SMS was indeed sent by the sender. But there is another intrigue. This was done from a previous iphone. Those. There is no SMS on the sending machine (in sent, received, drafts). Question: WHERE then lies this seductive SMS?

Answer 1

On bash, urgently.

Answer 2

Failure to split the SMS into pieces, most likely caused by a hash collision or overflow. And if this is a hash collision in the iPhone when splitting, queuing and sending, then the situation becomes even more interesting.

Answer 3

And there are an order of magnitude more views than in the nearby Q&A.
Everyone is wondering why. In IB.

Answer 4

It's funny.
Most likely, this is what happened:
When sending SMS from an iPhone, it was divided into two parts, because. longer than the usual 70 (like) characters.
Apparently, the second part of another message, from another person, caught on the beeline, and they got mixed up.
Those. someone received instead of an intimate message about "*I'm already bending over and I can't hold back my groans" - "now I've read everything ...". Or maybe he didn't.
I think that the other person's correspondence looked even funnier)
So, yes, this is most likely a beeline failure. The reason is most likely that the messages were sent second by second.

Answer 5

There is a description of a similar case here: infowatch.livejournal.com/382398.html

Answer 6

I had similar cases when in SMS notifications from the bank about card payments, half of the message refers to another transaction made several months ago. I thought it was a bug in the bank software. I use Android, Galaxy Nexus.
As far as I understood from all these cases, the added part is always taken from previously received SMS, and received from this particular subscriber. Therefore, about groans, obviously the sender cannot restrain them :)

Answer 7

UPD2: intrigue number 1 is revealed: the stuck SMS was indeed sent by the sender a long time ago. But there is another intrigue. This was done from a previous iphone. Those. this message is not on the sending machine (in sent, received, drafts). Question: WHERE then lies this seductive SMS?

Answer 8

I have observed this effect more than once, with friends on android (I sin on him, I have not observed it on other phones). Pieces from past posts.

Answer 9

Some kind of quest. is the sim one and the same?
just on a sim card you can store how many messages (200 or something). Maybe part of the SIM has migrated?