cdflasdkesalkjfkdfkjsdajfd

Do not exists a real need to include it with GOS at all.

I disagree, the following is a quote from the founder of GrapheneOS regarding the AOSP keyboard: (from the same github issue posted above)

Sticking with outdated code that's not being maintained is definitely not good for security, especially since it has a bunch of code unnecessarily written in C++ rather than Kotlin/Java.

And

Attack surface would be reduced by getting rid of C++ code and instead having almost entirely Kotlin/Java code that's memory and type safe.

So in my opinion, there is a need. I don't care honestly with what keyboard it would be replaced, but a replaced keyboard would mean it passed GOS audit, and an improvement securitywise.

    I have nothing against one particular choice of keyboard to replace the obsolete AOSP one. But last time I tried it FlorisBoard was less advanced than others (i.e. FUTO keyboard) for the integration of alternative languages. All the users of GrapheneOS are not white anglo-saxon protestants ;) /s

      I would be fine with florisboard if they decide to go that route. I will use whatever default keyboard they ship, more than likely.

        Eirikr70
        I think if they decide to replace the stock AOSP keyboard, it would be an upgrade nevertheless, either from a security standpoint aswell as a useability standpoint. Would u agree?

        If the potential replacement wouldn't suit the needs of some users, they are still free to use whatever keyboard they prefer.

        From that perspective, not much ultimately changes.

          lost_cause Their lack of autofill is the main reason I couldn't get behind florisboard, hope they add that eventually...

            Instead of including floris board and increasing attack surface, Floris board should looking to signup for Accrescent. And the FUTO keyboard is lightyears ahead of florisboard and has better auto prediction and speech to text. I not saying it should be included but the Accrescent idea would apply here as well

            But this is just my two cents as I don't speak for anyone

              OfflinePuffin Instead of including floris board and increasing attack surface

              Sounds like old, unmaintained code in the AOSP keyboard is already an attack surface, though...

                OfflinePuffin

                Instead of including floris board and increasing attack surface

                Can i ask u why u assume it would increase attack surface? IF they decide to replace the outdated AOSP keyboard, i'm assuming it will be audited by the developers of the GOS team before implementing. Just my thoughts, but my opinion is that it actually would decrease attack surface as it probably would get rid of unnecessary C++ code, and be written in a memory and type safe language, as i already quoted above from the founder of GOS.
                I'm not speaking of the current FlorisBoard, but of the FlorisBoard or whatever keyboard, if it got actually implemented by GOS.

                I'm not speaking for the GOS team, but i'm almost certain that FUTO it's license isn't 'compatible' with GOS.

                • TGOS replied to this.

                    I wouldn't recomend any special keyboard app to the devs ; they have their own criteria such as licensing, privacy, security or architecture/technologies. So I would just let them do the choice. My previous post was just meant to say that FlorisBoard is not, for me, an obvious choice in terms of functionality. It might be for other criteria.

                    DEADCAT
                    Just wondering, I remember that the gos team was planning on adding florisboard but stopped because of the liscense of a new library. That library has since been removed. Will florisboard be added to grapheneos? Are they waiting on predictive text maybe?

                    I hope this day never come, my first keyboard opensource it was openboard, I love it but reading online FlorisBoard it was considered a good alternative to OpenBoard, so I decided to switch for 1 month to FlorisBoard, I think the worst decision I ever make in my life. There are so much features (that's a good thing), but there are so many bugs that was make me so nervous and frustrate. Some bugs are so stupid, for example that in a random moment the theme it changes itself, so in a 2am while you are using your phone and you are search something on google you see a light theme keyboard that blind you, or when you open your phone just for search something, and the keyboard it appears to be just a solid black color without the keys. (There are other bugs, but the bugs that were occurring to me every day were mainly these two.) I resisted only for 2 weeks.

                      5 months later

                      r134a

                      Half a year later to your question I coudn't find an answer why it should instead of decrease increasing the attack surface.

                      Using it a while now with "alternative language" I coudn't spot any problems with it.

                      So despite such Announcements and tending to it, I'm sure the devs will find the happy medium when necessary