LufyCZ

Not in this context. Bare metal means all packages and services installed and running directly on the host, not through docker/lxc/vms

Earth doesn't have any bills though, dues to the United Federation of Planets are set to start in 2161 at the earliest

it's satire

Yep, guess that'd do it.

You'd still have to handle transferring keys across your devices, every time you login on a new one.

Also, searching would probably not work, at least as well as it does right now, since all messages are indexed on the discord side, which they wouldn't be able to do without seeing them. Everything would have to happen on device, meaning the devide would have to store all messages.

They are exchanged between the two devices.

Have you tried using Signal on desktop? It doesn't offer history syncing. Cross device for whatsapp for example is also a terrible experience. Unusable for something like Discord.

For a seamless experience Discord would probably have to store the keys themselves, defeating the whole point.

You're actually joking with the "inviter providing the decryption keys to the invitee" part right?

The whole point why people use discord is that it's simple, this is a feature that'd only annoy the average person, and every single extra step is a disaster for user retention (look at any eshop study).

Stuff like this is completely irelevant to discord, the tiny subset of people who actually care will and should use Matrix / other solutions, because that's the people they were made for.

Do you want to explain how to do it better?

That's how joining a server and being able to see history works

But googlr fabok bad?

Yeah, but people don't like change, and I'd expect low level engineers to like it even less.

And looking at Linux, that shit still supports ancient hardware, being able to actually get rid of old code (that now has to be maintained alongside the new code) is gonna be a PITA.

I'm just guessing, but what about backwards compatibility? Or cross-system compatibility?

For example, something like a syscall that's existed for 20 years. Changing it would break old apps.

Of course you could just keep the now "old" syscall and add new methods that replicate it's behavior, but haven't you then introduced bloat? More ways to do the same thing, meaning (eventually) more bugs, more fragmentation, memory usage, etc.