So, here are some basic suggestions I just thought of when I installed this program after 5 years and began looking around.
1. Ability to access user info from messages. Say that I have someone random who sends me a message. I should be able to pull up their user info.
Scenario: Someone mesages me letting me know who they are, which matches to someone I already know. I go to add them to my contacts, and cannot! I must know how to spell their name from hearing it alone as no place in the messages view lets me review a username to search, and what if they're offline?
Implementation: On the context menu of messages, conversations etc, there should be a view user info item that opens the same info menu you would get if you clicked on a user in other areas. If this works for mul.tiple people in a conversation, it should be a submenu that lets you pick a user, or perhaps a brief chooser.

2. Programs don't have descriptions.
I went to the install programs list and ran across some programs that I have no idea what they do. YouTube was explanatory enough, as are shooter and for me FFmpeg encoders, file manager etc, but what is saper? Klango archive? With the name alone, and no description giving a basic summary of the program, I'm unsure if I'd want to install it or not.
Implementation: After a program's name in the list a brief description, a few sentences at most, should be spoken. If you like, a larger description, help etc can be added as an extra item to the context menu of a program. This does create more text to localize, but the short description alone should be enough for the moment and relatively manageable.

The option for two-factor authentication should also support the use of TOTP-based authenticator apps and their associated backup codes, which are less cumbersome than SMS and also don't cost you anything to generate codes. These typically work with either a QR code scanned by the app or a textual secret entered into the app. I think if possible you should also support the QR code method, as so long as a blind person can vaguely point a phone at a screen displaying the code in a window of decent size, the redundancy in QR codes means it will likely be recognized.

Wow, I seriously didn't realise that the user stuff isn't there indeed, like it is in the list of users and in the forum! I agree to both of your suggestions.

TOTP can be sent to an authenticator app by copying an otp url or sending it by email. Than with your phone you can just open this url with your prefered auth app.

I mean the url with the otpauth:// beginning

Can you add a feature that lets us change the date format? If you can get it from a given locale, Ruby should be able to do that, or else a template to strftime? Depends on whether the server or client generate them I guess and where. It would be really cool if all events were listed in my local date format and time zone, which would change with my system clock. That would require basically sending datetime objects across with a known time zone, probably UTC< and having the client do conversions, so is probably non-trivial.
For reference, my date format, and that of Americans in general, is mm/dd/yyyy, or strftime would have it as %m/%d/%Y. We do month first, whereas most of the world does day first. The usage of period as a separator causes issues with English synths, which say a date like 25.01.2024 as twenty-five point o one point two o two four, or maybe even zero instead of o. And even if they can parse it as a date, since the day comes first a US English synth would switch the order.