Neat idea, shame about all this misleading information though.
The website very strongly implies (1) the only way to predict words is by uploading every keystroke to central server,(2) every keyboard other than theirs do that and (3) the only way to get privacy is to download their product.
This is all complete lies of course. The prediction database is small enough that you can bundle it with app and run all prediction locally. The "upload each keystroke" part is completely optional -- some keyboards have no such functionality, and some keyboards require explicit opt-it via the easily findable checkbox.
It's a pity that the authors of such original ideas have to resort to lies to promote their product.
It's quite misleading, actually. GBoard uses Federated Learning [0] so that models are trained locally on the device and keywords are not sent to the central server. Both Google and iOS use Federated Learning, Federated Evaluation & Tuning, Differential Privacy, and other privacy-preserving AI techniques and/or on-device ML to avoid sending user data to the server. Both have done so publicly since 2017 and have published many papers and talks on the subject.
> The prediction database is small enough that you can bundle it with app and run all prediction locally.
I don't think this is necessarily true. It really depends on what you're trying to predict. That said, I would agree that it should be 100% optional for your keyboard to have network access.
> Smartphone companies like Apple and Google, in an attempt to better their word prediction algorithms, as well as collect potentially profitable information on what their users were typing, began submitting and aggregating all their user's key-taps to their servers, violating user's privacy in the process.
Neither Google's nor Apple's keyboards send your keystrokes to the server, that would have been too outrageous, even for them. Gboard is kind of leaky, as it uses "federated learning" where the keyboard finetunes a prediction model locally, then the results are sent to the server and merged there; this is literally a long-term profile of what (and how) you type, and can probably be used to identify you elsewhere. But even then it doesn't send your keystrokes directly.
I think you know, but just to be clear: this one isn't T9, it's something IMO much better. I've used the keyboard they based this on and it's easily the best input method available on a phone once you learn it.
Just for the future record. The repository owner removed my comments and blocked me when I said that it may be unethical to ask for unpaid pull requests and other contributions if the developer explicitly says that he is going to charge users subscription fees.
If you want to make unpaid contributions into this project you should carefully consider this.
For the love of god... just show me how it works. Yes, based on a previous product. Yes, privacy is nice. Highly configurable. History of phone keyboards...
"Tap, or slide / swipe to type a letter."
Slide/swipe how?
"Swipe up or down on A to capitalize."
So is A acting like a shift key? Or is that for every letter? How to capitalize the letters then that I somehow have to slide/swipe on?
Dessalines, the author, also is the main contributor of Lemmy (an open source Reddit clone in Rust that's on the Fediverse). He's a very ideologically motivated programmer, a socialist, and I admire him very much.
Is anyone actually faster on this (or Messagease) than on a normal phone keyboard?
I may have put more than an hour into it already, I'm still only at a bit more than half my speed on Gboard, and my speed with Thumb-key already may have plateaued. It's easier to make mistakes on Gboard, but the speed makes those mistakes worth it anyway.
I did spend something like infinity time learning to type on a normal keyboard, so the comparison is uneven, which is why I'm interested in other peoples' experiences.
I used to use a very similar looking/functioning keyboard way back on my Palm organiser and then on my Pocket PC. I don't recall the name of it now, but I got be being quite fast with it. It didn't have any autocomplete IIRC.
On my Pocket PC devices I used a keyboard that looked similar, but functioned very differently. You would draw a letter in a 3*3 grid, the passage of grid squares would indicate which letter is being drawn. I loved it, I should write something similar for Android.
I experimented with a similar concept myself[1] but couldn't get myself used to it. The neat thing though is that it doesn't require a dictionary. You get what you type (or swipe), there's zero guesswork involved.
I'm missing some information on how this relates both to GKOS and particularly KeyBee! I did a survey of these different input methods many years ago[1]. Shame things haven't developed much since!
The website very strongly implies (1) the only way to predict words is by uploading every keystroke to central server,(2) every keyboard other than theirs do that and (3) the only way to get privacy is to download their product.
This is all complete lies of course. The prediction database is small enough that you can bundle it with app and run all prediction locally. The "upload each keystroke" part is completely optional -- some keyboards have no such functionality, and some keyboards require explicit opt-it via the easily findable checkbox.
It's a pity that the authors of such original ideas have to resort to lies to promote their product.