• 2 Posts
  • 49 Comments
Joined 3 years ago
cake
Cake day: June 4th, 2021

help-circle
  • Having unique one-time (non-reusable) invite ID is great.

    The wat SimpleX uses one-way queues, and then distributes those queues among servers offers a way to mitigate communication correlation (if the servers are independent and won’t collude). Or you can just self host and not worry. Self hosting an onion service is easy.

    Running SimpleX through a tor proxy (or VPN) offers even more advantages (if you think you need them).

    Perhaps the only downside is SimpleX still controls who gets to be a public server (anyone can self host or offer servers, but they won’t be integrated). I have no way of knowing if the servers are owned by a single entity. This part is not “open”.


  • Glad chomp/silence has worked out for you. Btw…SimpleXChat is different by protecting your social graph and not needing to share your private profile ID to contacts (via one time use invite codes). Can also be used on iOS/Android and hoping one day a desktop app GUI (not just a console app). Also has audio, video, file transfers, and groups. If really into privacy, you can host your own server and/or use Tor. https://github.com/simplex-chat/simplex-chat#roadmap

    What has really impressed me is how they are solving some of the industry problems (decentralization, privacy, metadata, etc); it’s not just another communication platform, it’s different.


  • I’m curious if the most up to date version, v4.2.1, has the battery consumption issue (or if there’s a configuration setting to change). Maybe it is just Android, not iOS, and curious about the differences.

    The developers are very active and responsive, so I hope if the issue still exists it gets reported and the devs have the opportunity to fix it.


  • Did you report the battery problem on github or their subreddit?

    I’ve also read these recommendations:

    1) Switching from instant notifications (default) to periodic - some users say it does reduce battery usage.
    
    2) If you are often reconnecting to the messaging servers - it may be happening on slow/unstable mobile networks - please try enabling dev tools and then increase connection timeouts in advanced network settings. It might result in fewer reconnections and reduced battery usage.
    






  • Lynda@lemmy.mltoPrivacy@lemmy.mlTox Chat
    link
    fedilink
    arrow-up
    3
    ·
    3 years ago

    Many of the top tier messaging platforms are trying to solve today’s problems and vulnerabilities. I like that Tox does not require a huge centralized infrastructure (only DHT) and is P2P. Tox is very fast and works well over Tor too. However, P2P, DHT, and limited infrastructure has it’s own challenges.

    I think Session and Status.im are better positioned.









  • I like Tox over Tor…really fast. But offline messaging is a problem.

    I don’t like Briar because it is Android only.

    I don’t like XMPP/Matrix because its more technical with too many options. I also want something anonymous. I also prefer not having a centralized server to connect or relay messages. You can accomplish these things, but its not simple for the average user.

    Signal would make my list if I didn’t have the hand over my phone number.

    Status, Session, and Tox+Tor are my favorites right now. Mainly because they do everyone I want without me having to do anything. Session seems to be more mature and active. Status has some interesting concepts, but it is too soon to see how they’ll workout, or someone from Status needs to do a lot better job of explaining it to me. So Session is my goto.