Real sad what happened there.

Yes, I get that people need to eat, but goddamn it man THERE ARE OTHER WAYS TO GET MONEY THAN SELLING OUT.

Ah, fair enough. Lol. I was hoping you were making a Fallout: New Vegas reference. Haha.

Ave, true to Caesar.

the “B” is in fact capital, I recently learned

I didn’t quite realize that. Thank you for letting me know!

Sorry, I may need to edit my original comment. I didn’t intend to imply that it’s bad. It’s not that great, but it’s not necessarily bad, to be fair. It’s just…meh. And honestly, I imagine that’s largely due to the fact that unlike the big name keyboard app makers, a lot of FOSS keyboards—Heliboard naturally being one of them—don’t track everything under the sun. Which is a good thing and something I like, make no mistake. The unfortunate downside of that is it’s also not quite as accurate, simply due to it not having as many data points.

This is not something I blame it for, but at the same time I was hoping perhaps another keyboard might have a prediction system different enough to be slightly better. Then again, I’m no expert on keyboard prediction systems so I probably should’ve kept my mouth shut in the first place. So apologies for that. :/

I feel autocorrect in general has gotten worse in the last decade or so. One problem I noticed, for example, that I’ve faced in other FOSS keyboards, not just in Heliboard, is that compared to ten years ago or so, there is a LOT more instances of autocorrect not catching absolute gibberish (like I get a couple letters off and it doesn’t catch it) or I’m one letter off of a very common word (like 1 key to the left or right) and it corrects it to something wildly different.

Maybe I’m just misremembering (after all, human memory is hardly ever reliable), but I feel it was a LOT better around the Jellybean era (for Android).

(Side note: this is all Android-specific; I have never owned any iOS device.)

Damn, I just switched from Bitwarden to KeepPassXC.

Clearly just in time. Lol.

What do you mean?

Thank you!

Thanks.

I…can’t tell if you’re serious or making a joke. Lol.

There’s another comment that mentioned a landlord that was published exactly 30 seconds before yours. :P

^{(Please keep in mind that I’m just teasing you. Obviously, there’s no way you could have known.)}

What is “big iron”?

• “Because Proton are not accepting contributions, they own all the copyright, so can make the code closed source again if they want to (that wouldn’t affect the already released versions, but future versions)”

They can’t do that actually. They can close the source, yes, but if they do they can’t then release the new closed-source version to the public.

From the GPL FAQ page:

Does the GPL require that source code of modified versions be posted to the public?

The GPL does not require you to release your modified version, or any part of it. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization.

But if you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the program’s users, under the GPL. [Emboldened by me.]

Alternatively:

Can the developer of a program who distributed it under the GPL later license it to another party for exclusive use?

No, because the public already has the right to use the program under the GPL, and this right cannot be withdrawn.

• “They could likely take down any derivative on iOS, since Apple will always take instruction from the copyright holder, for GPL’d code”

Does the license prohibit this? Definitely. Could they get away with it? Probably. Though I’m uncertain Proton would go that far. I mean, if they wanted to prevent forks, they wouldn’t have released the source, let alone with the GPL3 license, which requires the right to make modifications (as that’s one of the Four Freedoms).

• “Since the builds are not reproducible, there’s no guarantee that the binaries they distribute are built from the source code”

Technically true, I suppose, though again why they would do that is beyond me. If they didn’t want forks, they likely wouldn’t have allowed forks.

Again, this is all assuming I’m understanding the GPL FAQ page correctly. If I’m wrong, I would welcome someone smarter than me to correct me. :)

Well yeah. I mean, computers back then weren’t just spyware in a Scooby Doo mask.

That’s how I see it, too.

First make it so you can eat. Then you can deal with any privacy holes you need to fill.

That is...extremely unfortunate.

Is the autocorrect any better than Heliboard?

That is so weird. Haha.

I didn’t know that. Thanks!

Which distros, out of curiosity?

Maybe. I’m busy right now.

I might do it later. Maybe I’ll do it on

🎵 FRIDAY FRIDAY GOTTA GET DOWN ON FRIDAY 🎵