Matrix doesn't require you to set up a server.
Hopscotch
joined 3 years ago
@whatever and @Flyswat, you're right, it still happens with Jerboa 0.0.42. I didn't realize the behavior was related to the specific keyboard in use.
Thanks for posting the GitHub link.
Yes, and it is very annoying. ~~However it does not seem to be happening now with Jerboa 0.0.42.~~
Edit: This is still happening for me too, as of Jerboa 0.0.42, with the AOSP keyboard. It does not happen in any other apps.
I recommend using Molly instead if you need to communicate with Signal users. Note, the Molly-FOSS flavor excludes proprietary Google libraries entirely.
If you are interested in trying an alternative that is unrelated to Signal, I suggest looking at SimpleX Chat.
Just FYI, Signal (Open Whisper Systems) is not FOSS-friendly. The server-side software is not open source, they refuse to federate with other Signal implementations, and they are unfriendly to forks. See:
It's ironic but unsurprising, and my experience too, that some functionality works better with Nouveau than with the proprietary Nvidia drivers.
If you haven't already, check for Nouveau support. And if your card is supported, you may need a kernel parameter. I needed nouveau.config=NvClkMode=15 (but be warned some parameters like that have some risk, like possibility of overheating, and may or may not be applicable or safe for your GPU).
For me, it has worked to just set environment variable DRI_PRIME=1 to use the Nvidia GPU for that specific application. (Maybe this is what Bumblebee does; I don't know.)
In the future, though, I recommend avoiding Nvidia hardware.
As I mentioned in another comment, in my experience Nouveau does a much better job with multi-display and multi-GPU systems than Nvidia's proprietary drivers. Unfortunately Nouveau's actual hardware support is somewhat limited, so that is only relevant for a subset of Nvidia GPUs.
I, too, don't want any more Nvidia hardware.
In my experience they just work once you install proprietary drivers
That's not my experience with dual-GPU (Intel+Nvidia) hardware and multiple displays, where the standard xrandr functions are often used to modify the output configuration.
In my case, the Nvidia GPU is supported by Nouveau, so I can compare it with Nvidia's proprietary drivers "side-by-side". With Nouveau, display output configuration and per-application GPU selection both "just work" (I did add a nouveau.config kernel parameter to enable acceleration). I've never been able to make the proprietary drivers do those things reliably.
So I suggest that users with simple single-display, single-GPU systems are likely to have a better experience with the proprietary drivers.
As is the general consensus here, I do not plan to purchase any Nvidia GPU hardware in the future, especially considering that more recent Nvidia GPUs now require signed firmware, making Nouveau support impossible.
From the README at the current published commit:
Prior to this, releases occurred quite regularly.