Telegram quality

[vyamkovyi]

Some harmful things down there, prepare to get offended!

• The sound in Telegram is terrible. Unable to test precisely with mobile Telegram, but true for the official desktop version.
• Telegram started draining a lot of energy since calls was invented. I'm not sure about reports, since reporting such issue requires collecting a lot of technical data.
• Maybe it worths thinking about telemetry? The word "telemetry" is considered harmful, but under such conditions it would be good for developers to know about Telegram average battery drain and other similar but still useful things.
• The. God. Damn. Leaks. I'm not even talking about this or about the indian code itself, but there are damn leaks (actually even in mobile version but unable to confirm). More, MORE, Even Valgrind report (actually quite outdated, but things aren't getting better). Not even talking about security: it is broken simply because Telegram leaks just like a japan girl.
• Even this isn't going to backport UI/UX changes. You guys broke the user experience, just like Gnome. It was perfect. Please, get in touch with people!

Take this as an act of rage. But I've just grouped all critical things that require (but do not receive) attention. Later I'm probably going to increase this list.

you should have expected someone to make this

[john-preston]

1. (sound) fixing pull requests are welcome.
2. doesn't belong here, this repository is about Telegram Desktop only.
3. doesn't belong here as well.
4. why procxx/kepka issues? Telegram Desktop keeps all messages and images in memory, so the memory consumption grows, security is irrelevant here.
5. I don't even understand what's your problem here.

[vyamkovyi]

2. So laptops don't exist at all.
3. I disagree with your answer.
4. Sorry, but you're saying sanitizers are wrong.

[john-preston]

2. You've linked android screenshots and issues. Power consumption can't have anything to do with calls on desktop.
3. There could be some real leaks as well, but should not be much, there is still small amount of manual memory management. Fixing pull requests are welcome as well.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.