Remove profanity from autosuggestions and autocompletions

Terms

I have searched open and closed feature requests
I agree to follow Scribe-Android's Code of Conduct

Description

Note

This issue is blocked by the following issues:

We need to remove profanity from the autosuggestions and autocompletions for the keyboard application. This can be done once we export the profanity table as a part of Scribe-Data and then serve this data from Scribe-Server. The work to do this is done in the above listed issues in the note.

The way that we'll do this is remove any strings that contain a profane word from autosuggestions or autocompletions and move to the next word for the displayed field.

Contribution

Happy to support on this and review a PR! 😊

@angrezichatterbox

CC @angrezichatterbox and @Roniscend 👋 I thought it made sense to make a new issue so that in #660 we can just focus on the autosuggestions and the emojis. Then we can finish up the profanity issues in this issue 😊

@andrewtavis

Hi @andrewtavis, Can i work on this issue?

@Femimat

Hey @Femimat 👋 We could certainly use some help from you here once this issue is unblocked :) Let's be in touch once we have the data in Scribe-Data and in Scribe-Server.

@prince-0408

Till then, if you wanted to work on some of the points in #426, then that would be great 😊 @prince-0408 is working on that one too, but there are some subtracts that you can see in the checkboxes of the issue. @prince-0408 could also let you know what would help there :)

@andrewtavis

Alright, @andrewtavis. I’ll take a look at what I can work on there and see how it goes.

@Femimat

Till then, if you wanted to work on some of the points in #426, then that would be great 😊 @prince-0408 is working on that one too, but there are some subtracts that you can see in the checkboxes of the issue. @prince-0408 could also let you know what would help there :)

Hi @Femimat 👋

Welcome! Parts 1, 2, and 3 of the refactoring roadmap for #426 are already completed and merged.

I am currently working on:

Part 4: Introducing ScribeLanguage Enum to replace raw string comparisons.
Part 5: Removing language-specific layout assumptions from the base class.

If you'd like to help, you are more than welcome to pick up Part 6: Replacing Non-Null Assertions (!!) in keyboard services with safe calls! Let me know if you need any context to get started. 😊

@prince-0408

Hi! @prince-0408, Thanks for the warm welcome and for pointing me in the right direction.

I’d be happy to pick up Part 6: Replacing Non-Null Assertions (!!) in keyboard services with safe calls. I’ll take a look at the relevant code and get started. I’ll reach out if I need any context or clarification along the way. 😊

@Femimat

Thanks for the conversation, both of you! @Femimat, feel free to assign yourself on #426 as well to reflect the work you're taking on 😊

@andrewtavis

Alright, @andrewtavis. I will, thanks! 😊

@angrezichatterbox

@angrezichatterbox, we're now ready to work on this now that #715 is in! 😊

Navigation Menu

Repository navigation

Remove profanity from autosuggestions and autocompletions #665

Terms

Description

Contribution

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Remove profanity from autosuggestions and autocompletions #665

Description

Terms

Description

Contribution

Activity

andrewtavis commented on Aug 8, 2026

Femimat commented on Aug 13, 2026

andrewtavis commented on Aug 13, 2026

andrewtavis commented on Aug 13, 2026

Femimat commented on Aug 14, 2026

prince-0408 commented on Aug 14, 2026

Femimat commented on Aug 14, 2026

andrewtavis commented on Aug 14, 2026

Femimat commented on Aug 14, 2026

andrewtavis commented on Oct 27, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions