

For context, Debian dropped support for 586 in Debian Stretch (9.0), release in 2017.
I have not done the legwork to compare this to other distros, but Debian generally supports older hardware than most other major mainstream desktop distros.
For context, Debian dropped support for 586 in Debian Stretch (9.0), release in 2017.
I have not done the legwork to compare this to other distros, but Debian generally supports older hardware than most other major mainstream desktop distros.
Or perhaps you do not understand how Discord is commonly used.
People join dozens of servers. Maybe one for every game they play, every TV show they watch, every podcast they listen to. Everything has a Discord.
Even small Discord servers have many channels. Bigger ones will have dozens or hundreds of channels.
Some servers have millions of users. Most of the servers I’m in have thousands.
Many channels are default for all users in the server.
Not sure what the mathematical average is, but this is certainly common at least, and any alternative that can’t handle this is no alternative at all.
If we’re talking about Matrix as a Discord alternative, then that would mean thousands of channels, each with hundreds or thousands of users, many with constant activity.
I’m not sure if anybody actually uses Matrix at the scale of the average Discord user. Sliding sync is supposed to help, but I don’t think the Matrix architecture can realistically scale that high.
I set up their accounts
Setup is the hardest part. Syncing multiple devices and device migration are also hard. I’ll bet you’re going to act as tech support every time they get a new phone. That’s fine for your family, but it’s hardly going to scale.
The performance issues show up when dealing with large groups syncing between instances. You might just not be using it that way, but that’s what needs to work seamlessly for a viable substitute for Discord.
Matrix is notorious for its poor performance with large/numerous groups. They keep claiming to improve it, but it’s still bad.
I mean, it’s great that it works for you, but be honest: isn’t your tolerance for technological friction a bit higher than the average bear’s? People complain that Mastodon is too hard, and Matrix is ten times worse to sign up for and use.
I hate to say it, but Matrix is never going to be mainstream. Its UX is bad and it seems like it’s too bloated to fix. If I tried to get people to move from Discord to Matrix, they’d never take me seriously again. It was hard enough getting people to move from Facebook Messenger to Signal.
Where was all this coming from? Well, I don’t know what Stern or Esquire’s source was. But I know Navarro-Cardenas’, because she had a follow-up message for critics: “Take it up with Chat GPT.”
The absolute gall of this woman to blame her own negligence and incompetence on a tool she grossly misused.
I guess I’ll look into XFS and see if it’s suitable for my use cases (I know almost nothing about it), but this supports my opinion that BTRFS is an easy choice over EXT4 at least.
Edit: No snapshot support in XFS, so I’ll stick with BTRFS. My performance requirements are not that high on desktop. If I set up a high-performance server that would be another matter.
I was surprised to learn that F2FS has rather small maximum volume sizes. 16TB with 4K block sizes, 64TB with 16K block sizes. But your whole kernel needs to use 16K pages to use 16K F2FS blocks, which seems like more trouble than it’s worth. Either way, it’s so non-future-proof I’m not even going to think about it.