3 ms·
Tons of those, plus repeats, and "random" delays. Sometimes it takes a few minutes for messages to go through (single check). Last week was really bad. I don't
by MichaelGG 10y ago
Tons of those, plus repeats, and "random" delays. Sometimes it takes a few minutes for messages to go through (single check). Last week was really bad. I don't know how multiple messages can happen; shouldn't they have a unique ID?
- uph 10y agoLast week was due to server issues https://whispersystems.discoursehosting.net/t/intermittent-message-send-failures/537/7 https://whispersystems.discoursehosting.net/t/intermittent-m...
- Canada 10y agoI saw the mailing list post, then got the bad messages a day later. Probably the same issue, still curious about the technical details though.
- Canada 10y agoYeah. My understanding is the message key used to decrypt first copy should be immediately deleted after decrypting it, so how can the second copy be decrypted successfully? Seems to fly in the face of forward secrecy unless it's purely a client side bug. Bad encrypted message, if I recall correctly, means either the MAC check failed or the protobuf payload inside didn't deserialize correctly. I don't know.. I'm not setup to debug it on my regular phone with a production signal apk installed.
- newscracker 10y ago> and "random" delays. Sometimes it takes a few minutes for messages to go through (single check). This was the main reason I almost stopped using Signal several months ago and started trying out Wire (which is also slower when compared to Telegram). I find it disappointing that the problem still exists. I can't convince others in my circle to use it if basic message delivery is flakey and slow.