4 ms·

Reminds me how the telegram founder boasted how talented his team is as only one developer was responsible for writing the mobile client. Turns out that client

by siva7 2y ago

Reminds me how the telegram founder boasted how talented his team is as only one developer was responsible for writing the mobile client. Turns out that client was riddled with bugs that displayed messages to the wrong user. A mobile chat app shouldn't be developed with the mantra "move fast and break things" yet this is the natural product result of all-in-one apps like kakao.

deleted 2y ago
[deleted]
inquirerGeneral 2y ago
Was this a decade ago? I've been following Telegram development for over five years and never heard of this
- sunaookami 2y ago
  Telegram user since 2014 and never heard of it. This definitely never happened.
  - juanani 2y ago
    [dead]
bluesign 2y ago
To be fair to telegram; similar things happened to many big names: facebook, google, apple etc
- lxgr 2y ago
  Delivering messages to the wrong recipient!? Examples, please!
  - webappguy 2y ago
    Curious to know more. Will search but if anyone finds anything
    - bluesign 2y ago
      There are many examples, I posted one to parent. Usually it effects some small percentage of users. But size of the team or company not directly solving the problem.
  - wiseowise 2y ago
    How could client deliver messages to the wrong recipient? Why would client have messages for user outside of the one logged in anyway?
    - ascar 2y ago
      Seems like a rather easy thing to go wrong in the client, no? User sends message via client. Client fumbles the recipient id. Message ends up at the wrong recipient. Examples: incorrect recipient ID attached to contact in list where users selects recipient. Buggy selection of multiple targets in the selection UI due to incorrect touch event handling. Incorrect deletion of previously selected and then deselected recipient from recipient array of multitarget message. Or if working low level even a good old off by one error and reading out of bounds data for the recipient list (though that one hopefully should trigger a faulty send request due to other stuff no longer matching). There is endless examples. The server can't really safeguard against the client providing a legitimate send request even though the user intended to send it to another recipient.
  - ChrisClark 2y ago
    https://news.ycombinator.com/item?id=27950763 https://news.ycombinator.com/item?id=27950763 Yeah, I don't know how they manage to get bugs like that, but it's happened
  - bluesign 2y ago
    https://amp.theguardian.com/technology/2013/sep/26/google-privacy-bug-sent-chats-to-the-wrong-people https://amp.theguardian.com/technology/2013/sep/26/google-pr...
IncreasePosts 2y ago
Do you mean something like the mobile app had multiple user accounts added to it, and it displayed messages for one account in the other account? Otherwise it seems more like a server bug than a client bug?
BiteCode_dev 2y ago
Chat apps are hard, this doesn't strike me as a proof of bad quality as many competitors had such bugs. And Telegram has been so far the most reliable, feature full and easy to use chat app I have had to use.
- lxgr 2y ago
  Which other chat app has displayed messages to the wrong users? That seems like one of the worst things a chat app could possibly ever do.
  - asddubs 2y ago
    https://news.ycombinator.com/item?id=27950763 https://news.ycombinator.com/item?id=27950763
    - EGreg 2y ago
      Wow, touche And in an Apples-to-Apples comparison, WhatsApp fared far worse than Telegram on privacy, and not to mention its parent company. The only benefit I can think of WhatsApp has is claiming to be encrypted by default. So I dont need to press an extra button. I just have to take their word for it.
      - lxgr 2y ago
        > And in an Apples-to-Apples comparison, WhatsApp fared far worse than Telegram on privacy, and not to mention its parent company. I'd like to see that comparison. Considering that WhatsApp is end-to-end encrypted, and Telegram persistently stores almost all of their users' messages on their backend in a way that lets them read them, I find that very hard to believe. > So I dont need to press an extra button. Nobody presses an extra button, especially not one that opts you out of multi-device support.
        BiteCode_dev 2y ago
        Whatsapp is not open source and facebook was part of the PRISM program. I don't think it's reasonable to expect them to actually be e2e encrypted. Espacially since Zuckerberg has many years of poor track record for privacy, and made the famous quote "they trust me the dumb fucks"
rvba 2y ago
"Designed by committee" software can have terrible bugs too.
doyoulikecheese 2y ago
Kakao definitely does not move fast...

by siva7 2y ago

deleted 2y ago

[deleted]

inquirerGeneral 2y ago

Was this a decade ago? I've been following Telegram development for over five years and never heard of this

sunaookami 2y ago
Telegram user since 2014 and never heard of it. This definitely never happened.
- juanani 2y ago
  [dead]

bluesign 2y ago

To be fair to telegram; similar things happened to many big names: facebook, google, apple etc

lxgr 2y ago
Delivering messages to the wrong recipient!? Examples, please!
- webappguy 2y ago
  Curious to know more. Will search but if anyone finds anything
  - bluesign 2y ago
    There are many examples, I posted one to parent. Usually it effects some small percentage of users. But size of the team or company not directly solving the problem.
- wiseowise 2y ago
  How could client deliver messages to the wrong recipient? Why would client have messages for user outside of the one logged in anyway?
  - ascar 2y ago
    Seems like a rather easy thing to go wrong in the client, no? User sends message via client. Client fumbles the recipient id. Message ends up at the wrong recipient. Examples: incorrect recipient ID attached to contact in list where users selects recipient. Buggy selection of multiple targets in the selection UI due to incorrect touch event handling. Incorrect deletion of previously selected and then deselected recipient from recipient array of multitarget message. Or if working low level even a good old off by one error and reading out of bounds data for the recipient list (though that one hopefully should trigger a faulty send request due to other stuff no longer matching). There is endless examples. The server can't really safeguard against the client providing a legitimate send request even though the user intended to send it to another recipient.
- ChrisClark 2y ago
  https://news.ycombinator.com/item?id=27950763 https://news.ycombinator.com/item?id=27950763 Yeah, I don't know how they manage to get bugs like that, but it's happened
- bluesign 2y ago
  https://amp.theguardian.com/technology/2013/sep/26/google-privacy-bug-sent-chats-to-the-wrong-people https://amp.theguardian.com/technology/2013/sep/26/google-pr...

IncreasePosts 2y ago

Do you mean something like the mobile app had multiple user accounts added to it, and it displayed messages for one account in the other account? Otherwise it seems more like a server bug than a client bug?

BiteCode_dev 2y ago

Chat apps are hard, this doesn't strike me as a proof of bad quality as many competitors had such bugs. And Telegram has been so far the most reliable, feature full and easy to use chat app I have had to use.

lxgr 2y ago
Which other chat app has displayed messages to the wrong users? That seems like one of the worst things a chat app could possibly ever do.
- asddubs 2y ago
  https://news.ycombinator.com/item?id=27950763 https://news.ycombinator.com/item?id=27950763
  - EGreg 2y ago
    Wow, touche And in an Apples-to-Apples comparison, WhatsApp fared far worse than Telegram on privacy, and not to mention its parent company. The only benefit I can think of WhatsApp has is claiming to be encrypted by default. So I dont need to press an extra button. I just have to take their word for it.
    - lxgr 2y ago
      > And in an Apples-to-Apples comparison, WhatsApp fared far worse than Telegram on privacy, and not to mention its parent company. I'd like to see that comparison. Considering that WhatsApp is end-to-end encrypted, and Telegram persistently stores almost all of their users' messages on their backend in a way that lets them read them, I find that very hard to believe. > So I dont need to press an extra button. Nobody presses an extra button, especially not one that opts you out of multi-device support.
      - BiteCode_dev 2y ago
        Whatsapp is not open source and facebook was part of the PRISM program. I don't think it's reasonable to expect them to actually be e2e encrypted. Espacially since Zuckerberg has many years of poor track record for privacy, and made the famous quote "they trust me the dumb fucks"

rvba 2y ago

"Designed by committee" software can have terrible bugs too.

doyoulikecheese 2y ago

Kakao definitely does not move fast...