v2.0-beta

Changelog

• Added voice chats
• Added automatic updates
• Using FQDNs instead of IPs is now possible
• Switched to HTTPS and WSS instead of HTTP and WS
• Added custom display names
• Signed and verified every network request necessary (requests such as closing the voice chat are not verified on the client's side, because if the server wants, it can just stop relaying the data without ever notifying the client. Therefore, verifying these requests, coming from the server, serves no point)
• Chats get marked as unread when they are unread and read when they are read
• Many, many bug fixes

The ability to have friends was also implemented, but it currently serves no purpose, as it is still possible to interact with others who are not friends.

v1.0-beta

The first fully functional version of SecureChat. This has all the features which are needed for a workable experience.

There are still many unhandled errors and HTTP is used for testing purposes. In the future, HTTPS will be used for further security.
It also crashes on first startup if there is not a server running on localhost. This can be fixed by the end user by setting a different ip address in the settings.json file if the user wants to connect to a server which is not running on localhost.