I initially tried FUTO and switched to Heliboard (which uses a closed-source glide typing library) because FUTO’s open-source version frankly sucked.
I didn’t know I could make it better.
Credit to @Nednarb44@lemmy.world :
It takes a lot of time and a lot of peoples typing data from my understanding. It’s relatively easy for Google to make the glide/Swype type since they have a huge amount of peoples typing data. FUTO on the other hand has been making an open source version for probably 6 months or so no, solely relying on volunteers inputting words on their website.
For those interested in helping make the library better: https://swype.futo.org/ (it
probablyonly works on mobile)
when futo dissolves as an organization, or someone forks their software and maintains it better than they do, that fork still has to have the button to pay futo and not the new maintainer.
there are restrictions on what you can do with the source. that is not open. the source is available and they’ll accept your donation of code, but you are donating to a company’s product, not a community project.
Yeah, I see what you mean. That makes sense. After reading through some common OSS licenses, I can see the difference between licenses that require you not to modify the license notification, versus software that explicitly forbids certain changes. But, given how little funding OSS projects get, I’m not bothered by the idea that they want to make sure people financially contribute to the original creators. After all, if someone does fork it and do a better job, they could easily just put their own donate button higher up above the original one.