Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
So does this affect English/European keyboards or just Asian keyboards?
It seems like the mechanism is exploiting an insecure connection (or rather a connection using predictable encryption where the same input results in the same packets) to the cloud for translating keystrokes into logographic characters?
Did I understand correctly? I definitely didn't do a thorough read.
I also think it's kind of interesting Gboard wasn't included (?)
It's about using a cloud-based model to better predict the next keystroke.
Think of the next-word-prediction of the likes of GBoard or SwiftKey, but for just strokes/characters. There's a local model, but it's limited in depth and complexity, and then a cloud based one, that can do more but as shown here has security flaws.
Well, it can't just be about that. There are ways to salt the data so that it's not predictable. I'm not an expert in that area, but I know it's a technique that's often employed by cryptography experts when this is a major concern.
Indeed. But given it's Google I would not be surprised if Gboard has keylogger features.
I think that would be far too large of a liability for Google for the minimal amount of data they'd get back.
Google mostly cares about metadata for their advertising business (per my understanding).