It was a many months transition, and it’s finally done

Fun thing, you can actually make a backup of all* your messages, groups, contacts, etc. So before leaving you can have all of your data in case you need that one contact or something

The final red flag was as that allegedly Russian authorities were messing with people’s deleted messages. Not for the first time there are news that they could read, modify, delete, see location, and etc. Screw it, this is unsafe, I’m out.

Also, these days telegram is really at the state of a pile of garbage, bloated, buggy, and shady messenger.

  • LWD@lemm.ee
    2·
    9 months ago

    I must have been thinking of their past implementations. Their FAQ says things were different:

    Proxy routing was an interim routing solution which Session used at launch while we worked to implement onion requests. When proxy routing was in use, instead of connecting directly to an Oxen Service Node to send or receive messages, Session clients connected to a service node which then connects to a second service node on behalf of the Session client… The proxy routing system has now been replaced by onion requests.

    It was even less clear to me because this is what it says in the app itself:

    Session hides your IP by bouncing your messages through several Service Nodes in Session’s decentralized network.

    Not “the Oxen network” but “Session’s network.”

    And then it has a graph of

    • You

    • Entry Node

    • Service Node

    • Service Node

    • Destination

    • Synnr
      2·
      9 months ago

      You’re not wrong. Lokinet and Session are both products from the same parent company. Lokinet was renamed to the Oxen protocol, and they run all the servers AFAIK, so it would be like tor, if tor ran every guard, entry, and exit node. AKA worthless. So you’re spot on, it’s a joy to the intelligence community and after the Encrochat debacle and Session stopped using Signal’s encryption algorithms and code, I would suggest no one use it for anything sensitive.