src.next VS OpenBoard

According to their github repo, it was last rebased with chromium version 105.0.5195.24, which was from August 2022. Using a 15 month old browser seems hilariously insecure.

https://github.com/kiwibrowser/src.next

I've never tried Kiwi Browser but had similarly come across it while searching. The dev interestingly refers to them ads[1] (2022), though prior to being accepted properly into Bing's referral program Kiwi redirected all search queries through their own servers[2][3] (2021) (the original Kiwi repo's issues tab has been deleted since).

Tbf dev always sounds reasonable in their responses but was a little off-putting initially so I kinda understand the GP's post.

[1] https://github.com/kiwibrowser/src.next/issues/91#issuecomme...

[2] https://github.com/Tobi823/ffupdater/issues/35

[3] https://web.archive.org/web/20210605191305/https://github.co...

Download the latest version of Kiwi Browser from it's original source like github Kiwi Browser GitHub Releases (Choose the 2nd one tagged ARM/64 if you're using it from Playstore rn, choose the first ARM/64 if you're using GitHub apks rn) OR Kiwi Browser July 21 UpToDown

com.kiwibrowser.browser-arm64-5624320950-github.apk231 MByesterday

Maybe I should also mention Kiwi Browser (Chromium-based) and Iceraven (Firefox-based) specifically for mobile.

Correct me if I'm wrong, but I thought they walked back on that? And I think the source code repo is now : https://github.com/kiwibrowser/src.next ? Maybe that's just the chromium rebase repo though.

Other things you could try: an older version of Kiwi Browser, or a version of Kiwi from the GitHub.

Yeah, that's the one I'm talking about. You can see here that it's only had one commit in the last 6 months

After reading a lengthy GitHub discussion at the Openboard repo that went into the logistical options and challenges I decided to go with the less-than-ideal option of using Helium314's Openboard fork with the proprietary Google swipe library (libjni_latinimegoogle.so) imported. I've been using it for a few weeks now and though it feels slightly different than the Gboard I'm used to, the difference has been negligible and I'll be sticking with this setup for the foreseeable future.

Pretty easy search ngl... https://github.com/openboard-team/openboard

Keyboard → OpenBoard (FlorisBoard when the v4 will be released...)

If you're willing to switch keyboards, OpenBoard has a fix for it.

You can give OpenBoard a try till florisboard is a complete app... And also... My case is also same in terms of boost... So imho the best thing you can do is used a cleaned apk of boost (basically a cleaned version of the app with all ads, trackers and analytics disabled)

OpenBoard and don't look back.

GBoard → OpenBoard (FlorisBoard when the v4 will be released)