rdri

So if an app doesn't support e2ee all data is being saved in plain text suddenly. You prefer calling telegram shitty because you don't care to actually learn what it uses. So it should be fair for me to call any other client shitty for other nonsense.

has been proven to have critical weaknesses

Those are not critical, just some aspects being below some arbitrary expectational values. Also it seems there is still no proofs those vector attacks are being used at all.

Yes it can

They chose to target convenience over max security. Shoving strongest options to every user by default is agaiantt that. Reasons include: no history is being saved in this mode, and the desktop client doesn't support it.

Signal has had group chats for many years now

Just because it was implemented by others doesn't mean it's a way to go for everyone. From what I understand, e2e in group chats means that there is going to be a transaction of keys between all members of the chat on adding any new member, and/or on new message, which excessively increases the burden on clients and servers in case of big active chats.

You can ask telegram to implement that, but you can't blame it for keeping it behind some gates. Telegram got implemented e2e between 2 users before other messengers got it working in any form of group chats.

and use Signal

I'll think about it if they ditch electron.

There is no normal e2ee because there is no standard for implementation, especially when it comes to group chats with >2 people.

Alternate clients are blocked from using that functionality because they may include ability to capture data somewhere, for example taking a screenshot of a protected chat.

Useless. Current allegations are related to the absence of moderation. Moderation of public content, in public channels or chats. As you can guess, end to end encryption does not protect public content.

That bad encryption was not cracked for now. The other one, that is used to process chats between 2 users in end to end mode, can't be enabled by default because it assumes no history is kept and no support for group chats.

Also, the arrest doesn't seem to be related to any of the things you mentioned. If anything it shows there are no ways for (certain) governments to affect the messenger, for now.

Companies mentioned in an article you linked aren't getting the cash flow enough to warrant any improvement in related economies. I see Russian politicians profiting off various things during war but they were doing the same before.

So, short effects of the war on economies are not worth the long term effects of deaths of many consumers anywhere. Using the "war helps economy" argument while forgetting how the deaths and active aggression affect the world and lives, is a manipulation, which is also heavily used by those aggressors (Russia).

Telling Israel is doing a genocide without mentioning what hamas were doing to Israel is also a manipulation.

Worldwide governments seem to have an interest in this war because they are doing everything to fuel it.

Bingo. This nullifies your credibility. Either you're a troll or an idiot.

You aren't addressing what I've said. But that's expected. No need to spend more of your time.

You want unlimited filename length??

No. But a limit at least better than Windows has to offer would help a lot (already because switching is a common thing and should be made breeze for everyone). And 256 bytes is bad no matter how you look at it.

Skills+time, or money to pay someone with the skills, that's what is needed.

No, that's not needed I think. Some file systems supported by Linux already support longer names, it's Linux VFS that is limiting them. This is an artificial limit basically. It will be changed eventually, I only say that it's long overdue already.

I assume you know of Stream's Proton and just Wine.

I assume you know it wasn't always like that. Surely a lot of Linux developers never thought it was a good idea to support many more windows-related systems (one could say it would be implemented if it was a big issue), but here we are.

You aren't getting it.

It's not about bricking, it's about relying on "standards" (limitations actually) that should be obsolete in 2024, in multinational technology world. About the fact that they are effectively limiting how people from all around the world can use characters, words, names etc. anywhere.

It's not about money, not about patches or developing them. It's about what users expect. They surely don't expect to be told "fix it yourself if you don't like".

This is by no means a "big" issue because it affects less than 1 percent of users, sure. Not many people hit the NTFS limit on windows either, yet you can see thousands places where people discuss that long paths setting, people who need to overcome it, people who maybe even grateful that such an option appeared in later windows versions.

It filename, not filesentence.

😒 Yep, that's useless. What's next, "hey Linux doesn't support .exe, those are games for windows so you play them on windows"?

clearly isn't as big an issue as you feel or it would be fixed.

I might have agreed with such statements 20 years ago. But not anymore. I can't count the times I've seen how certain software, game, system or a service literally brick themselves when a use case involves using non-ascii, non-english or non-unicode characters, paths or regions. Not Linux related only or specifically, but almost always it looks and feels embarrassing. I've seen some related global improvements in windows, NTFS, and some products, but all that is still not enough in my opinion. The thought that people shouldn't need >255 bytes (or symbols) sounds not different from that 640k ram quote.