Official news: MyChat 2024.3 — PIN codes, and erasing data secretly on Android

Release date: 29.03.2024

Development history

 
[+] new feature;

[*] fixed bug or improved feature;

[-] fixed.

 

MyChat Client

[+] (android) added option to use a PIN code for application protection;

[+] (win32) redesign of the navigation panel;


[*] (win32) geoiplookup.net stopped working, so we have started using another service for detecting MyChat users' IP location;

[*] (win32) if the application gets an error during the login process (incorrect password, login, unknown domain user, an incorrect domain password, etc.) — the app stops continuously connecting to the server and exits to account manager;

[*] (win32) when receiving an image in the active chat, the image thumbnails loads from the server, and the text array vertical size changes, the program knows whether to scroll it automatically down or not;

[*] (win32) opening/closing contact groups (Ctrl+3) by left mouse click only;

[-] (win32) rendering error in messages with smilies when loading history by mouse wheel scrolling or Alt+Up/Home: history is missing some messages. Fixed;
[-] (win32) option for disabling smilies does not work, fixed;
[-] (win32) disabling option for using smilies does not work in the settings templates that the application receives from the server. Fixed.

[-] Ctrl+PageDown after reconnection to the server on private dialogues could cause errors. Sometimes the index of an active private dialogue displays incorrectly too;

[-] (win32) fixed rendering for incorrect local links (e.g "1:", etc.);
[-] (win32) the tools for viewing history do not display edited messages, fixed;
[-] (win32) history rendering in conferences/private dialogues in the window for viewing history — issues with time stamps displaying;

 

MyChat Server

[+] a setting for using access PIN codes in mobile devices;

[+] technology for hidden deletion of all data, account blocking, and notifying an administrator about this event (panic pin code);


[*] increased the speed of the server's launch and restart process, especially when there are conferences with a large history. Sometimes, the time saved is 20 seconds or more;


[-] a bug in message delivery statuses in conferences and private dialogues when working with a couple of clients with different OS and connection speed;

[-] (admin) when creating a new settings template and the filter is on, then a list of the new template settings is not cleared visually. Fixed;

[-] error ID 33B3DAA7 occurs sometimes when requesting the history database, while a user is not a member of any conference.