For a few months I’ve spent my free time working on a C++ messenger. It started off pretty simple, just two input boxes for IP address and port number, more of a fun experiment. From there it started to grow and soon allowed for peers to connect automatically using a relay. For a while it only allowed two people to speak at once, which was good for security but was very inconvenient. Now Retro Messenger allows multiple users to speak at once, sending encrypted files and messages that exist only in memory.
Although there is plenty of things I could improve, I was curious to see if anyone had suggestions or requests for what else could be added. I’m currently debugging a local-logs feature, and I could look into how to implement voice calls in the future. Thanks for your time and feel free to ask questions
Landing page: https://retromessenger.space/
Would probably need to be open source to be trustworthy. Running a random executable from the Internet seems dicey.
Needs more screenshots. The two that are on the site don’t render great on mobile. Can only see a small portion.
I’m unclear how you find another user and verify who they are.
Website should have a clearer feature list. The user manual wants to download a text file instead of showing it in the browser.
Thanks for the feedback. Should I show snippets of the relay server code or the entire process? Could this be seen as a security risk or do you think the feedback and suggestions from more experienced programmers outweighs that? With the finding users thing, I suppose it’s a little tricky. I sort of imagined it as users connecting through other sites (or the public chatrooms in RM) and using Retro Messenger as a secure messenger, more of a secure, easy tool rather than something people are on constantly like Discord or Messenger.
For the code, open source is probably the way to go. People should be able to build from source. Otherwise, how do they know you’re not doing something shady. Open source is generally a net improvement on security, assuming people actually look at it.
For screenshots, first fix it so the screenshots render nicely on narrow displays.