Just as a warning, this is licensed under the AGPL, with a CLA that requires copyright assignment. So, they could pull the rug at any time:

2.3 Outbound License. Based on the grant of rights in Sections 2.1 and 2.2, if We include Your Contribution in a Material, We may license the Contribution under any license, including copyleft, permissive, commercial, or proprietary licenses.

It’s not perfect yet, but it’s much, much better than the old days.

OMEMO is supported by every major client, and they interoperate successfully. Unfortunately, most clients are stuck with an older version of the OMEMO spec. It’s not ideal, but it doesn’t cause any practical issue, unless you use Kaidan or UWPX, which only support the latest version.

All popular clients and servers support retrieving chat history now too.

In practice, I’ve been using it for several months to chat with friends and family, and haven’t had any issues.

Perfect, now you just have to wrap your program inside a debugger in production!

I originally suggested Monal to my friend (who is quite into iOS and really appreciates a well designed application) and she found the same, but then she tried Siskin, and was happy enough to use it to this day.

Just for reference, here are my favourites on each platform.

Each support modern XMPP extensions, interoperate very nicely with each other, and (at least in my opinion) look good!

• Android: Conversations
• iOS: Siskin
• Windows & Linux: Dino
• Mac OS: Beagle IM
• Web: Converse JS

As a note of caution, I used Oracle’s free tier to run a personal Matrix server, and it got deleted without any advance warning after a few months. I migrated to another provider and haven’t had any issues for 2+ years now.

Gotcha. Now I understand a bit more about the way input is locked down, it looks like I would need OpenSD to allow for more sophisticated controller input without using Steam.

Thanks for the reply, this is really helpful!

If you don’t, the Steam Deck will essentially behave as a Xbox 360 controller.

I see, this makes sense and I guess the “Xbox 360” experience will depend on whether the games themselves have native support for controllers or a very flexible input scheme.

the touchpads will not behave correctly

This is interesting, do you know what would be the difference between using the touchpads on other distros vs through SteamOS? Are they not just seen as a regular mouse input device by both OSs?

Thank you for writing up such a detailed response!

I run Debian on my laptop and tend to install FOSS games through the regular package manager. However, I don’t spend as much time playing these games as I would like, so when I was looking into the Steam Deck I was hoping that it would let me have a very similar setup, but as a portable device.

I see through your reply that, if I want automagic compatibility out of the box, this is crowdsourced and implemented through some intermediate Steam layer. I was hoping there might be some way to bypass Steam and treat the trackpads as regular mouse input, and map the other buttons as if they are keyboard buttons or generic controller inputs, without having to go through Steam.

I guess this would mean the FOSS games I’m interested in playing would need controller support natively implemented, which I’m not too sure on for the games I’m interested in. Probably time to dust off an Xbox 360 controller and see how they perform!