[feat] Word filter case sensitivity #431

New issue

Open

opened 2025-02-27 17:22:06 +00:00 by banaanihillo · 0 comments

banaanihillo commented

2025-02-27 17:22:06 +00:00

The idea

As it stands, the Settings > Filtering > Wordfilter input appears to be case-insensitive.

The issue author ran into some existing issues with mentions of regular expression filters, but is unsure if they're directly related and/or if said issues are still up to date.

This is a proposal for case sensitivity within said textarea input.

Said feature has been very briefly tested via the issue author's instance, and the patch with the minimal tweaks required onto the front end code can be seen in the link below:

banaanihillo/akkoma-fe@c9ab0c813d

The reasoning

If implemented, this allows for case-sensitivity within the front-end filters/word-mutes without more elaborate involvement within the back end.

Ideally, the user would be able to choose which input is meant to be case-sensitive, so as to retain backwards compatibility with the expectation of all wordfilters being case-insensitive, but that would probably require further tweaks.

Have you searched for this feature request?

I have double-checked and have not found this feature request mentioned anywhere.
This feature is related to the pleroma-fe Akkoma frontend specifically, and not the backend.

### The idea As it stands, the Settings > Filtering > Wordfilter input appears to be case-insensitive. The issue author ran into some existing issues with mentions of regular expression filters, but is unsure if they're directly related and/or if said issues are still up to date. This is a proposal for case sensitivity within said textarea input. Said feature has been very briefly tested via the issue author's instance, and the patch with the minimal tweaks required onto the front end code can be seen in the link below: https://codeberg.org/banaanihillo/akkoma-fe/commit/c9ab0c813d0302825695e449c1248947df67d712 ### The reasoning If implemented, this allows for case-sensitivity within the front-end filters/word-mutes without more elaborate involvement within the back end. Ideally, the user would be able to choose which input is meant to be case-sensitive, so as to retain backwards compatibility with the expectation of all wordfilters being case-insensitive, but that would probably require further tweaks. ### Have you searched for this feature request? - [x] I have double-checked and have not found this feature request mentioned anywhere. - [x] This feature is related to the pleroma-fe Akkoma frontend specifically, and not the backend.