Bad headline. She was not actually attacked by either one.
Hopscotch
Wouldn't it be far better to compare fuel cost per mile ($/mile)? This graphic seems useless to me. Maybe I'm missing something.
@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.
Is that from Hitchhiker's Guide to the Galaxy by Douglas Adams?
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:
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.
Matrix doesn't require you to set up a server.