Native Sliding Sync (AKA Simplified Sliding Sync) was just released to Synapse and Element X over the past couple of weeks. It’s not an exaggeration to say that it is FAST now. My fairly large account usually syncs instantly now. If not instant, the longest I’ve seen was 1 second. Give Element X a try again (assuming your home server supports SSS).
It still depends on the hardware you have. If you have hardware that’s fully supported by the kernel version your distro is running, then it’s easy. But as soon as you add a piece of hardware that isn’t, there’s a good chance you need to spend a lot of time searching how to fix it. Buying a new mouse and all of a sudden not having sleep work is not a power user problem IMO.
Unfortunately, Linux isn't quite there yet for casual users. I tried it every year, and there was always something that was annoying enough that I switched back to Windows with O&O ShutUp10. This is the first year that I've been happy enough with my install that I've started using it as my daily OS. But even this year, I had 2 really annoying issues that I had to spend time searching to fix.
-
After putting my computer to sleep, it would immediately wake back up. Eventually found out it was my Logitech wireless dongle that was causing the issue. I had to create a script that disabled USB ports during sleep and a systemd service to make sure it activated on every boot.
-
After waking from sleep, my screen was black with only my cursor visible. Running
sudo systemctl restart display-manager
sometimes worked, but that wasn't a solution. After searching the web some more, I found an arch wiki explaining that it was an issue with my Nvidia GPU. So then I had to edit a modprobe file and finally I was happy with my install.
I'm super happy that I can finally use Linux full-time, but the fact I had to mess around in terminal to fix the issues associated with my hardware means most casual users will just go straight back to Windows. I've seen a lot of Linux users say, "just don't use Nvidia", but buying a new GPU isn't a solution for most people. My hardware isn't even that weird: AMD 5800x3d, x570 chipset, Nvidia GPU. Linux is getting there, it's closer than it's ever been. But it's not there yet.
You can self host the bridges, but a lot of the "magic" happens on their clients. But if you're okay with a bit of inconvenience in setting up and bridging services, self-hosting bridges is definitely possible using another matrix client.
To be honest, I'm not sure what they were thinking when they released their reverse-engineered iMessage app. But I'm hoping they're back on two solid feet and will get back to focusing on their original mission because it'll mean more open source contributions back to the matrix project.
I'm not super excited about them getting bought, but at the same time I think it's better than the alternative. Beeper's CEO (now former after being bought) is infamous for creating the startup, Pebble, then running it into the ground by not selling it. As unfortunate as it is, the reality is that companies, even ones based on open source projects, can't survive without funding.
Yes, Beeper's apps are all closed source. But they do contribute a lot of their improvements back to the matrix community. For example, they've contributed quite a few performance improvements to the Synapse homeserver. They're also involved in getting new features supported on matrix such as media captions.
Using an all-in-one messenger like Beeper will always be less secure than using standalone apps because it can introduce another vector for attack. That being said, I believe Beeper is trying their hardest to stop "middle manning" your messages. For example, in their newest Android client they have an on-device Signal bridge which means your messages never get sent to Beeper's servers.
Personally, I am happy with the convenience of Beeper. I use it every day with multiple IM services linked and it has saved me a lot of time. I also love that Beeper is built on matrix and that they're contributing back to the open source community.
It’s good to know that future release cycles will be shorter, but it still feels a little bad on Media Segments because it seemed so close to being done. Oh well, I’ve been waiting years for proper intro/outro on JF, I can wait 6 more months :)
As it currently stands, they can’t let the user decide under the DMA. To do that they’d need to build an entirely new PWA API and put time into making sure browser engines other than WebKit can’t escape their sandbox. After they do that, then they can let the user decide since all web browsers would then be equal. But as the poster above you said, PWA install rates are very low outside of the small tech enthusiast circle so I don’t blame Apple for axing this feature under the time crunch. I do hope they re-visit this issue and enable PWAs for all engines though because I love the idea of PWAs.
tbh, I don't like where this new product seems to be taking Beeper. I was a giant fan of Beeper because they were a huge contributor to the matrix project. But with them creating an entirely new app that doesn't rely on matrix at all, it looks like they may be looking to pivot away and create their own client-side implementations rather than use matrix bridges. It would be sad to lose a contributor to the matrix space.
You might try a Matrix group instead. Doesn’t require a phone number and supports more than 1000 users unlike Signal. Search is bad though unfortunately.