this post was submitted on 04 Feb 2026
11 points (100.0% liked)

Connect for Lemmy App

3859 readers
1 users here now

A community for the mobile app Connect for browsing Lemmy and Piefed.

Links

founded 3 years ago
MODERATORS
kuro_neko@lemmy.ca
11
[BUG] Filters being ignored (lemmy.world)
submitted 6 months ago by HypnoticSheep@lemmy.world to c/lemmyconnect@lemmy.ca
4 comments fedilink hide all child comments
 

Bug Report

Describe the issue: It seems filters are not applying now, or possibly just not being respected. It may have to do with capitalization- it seems posts containing filtered words are allowed through if the first letter is capitalized.

Steps to reproduce:

  1. Add "trump, Trump" to the filter list.
  2. Browse All.

Device Information

  • App Version: 1.0.388 (388)
  • Platform: android
  • OS Version: AP3A.240905.015.A2.G998USQSJHZAA

Modified Settings

The following settings have been changed from defaults:

  • isSwipeEnabled: false (default: true)
  • alwaysShowInstance: true (default: false)
  • isSwipeNavigationEnabled: false (default: true)
  • shouldLimitCardImages: true (default: false)
  • shouldMarkPostsOnScroll: true (default: false)
  • shouldHideReadPosts: true (default: false)
  • shouldShowPageNumbers: true (default: false)
  • isTopBarFixed: true (default: false)
  • showFullVotes: true (default: false)
  • shouldAlwaysDisplayAvatars: true (default: false)
  • shouldOpenYoutube: false (default: true)
  • defaultPostSort: TopTwelveHour (default: Active)
  • defaultCommentSort: Top (default: Hot)
  • postActions: [comment, save, read, crosspost] (default: [comment, save, none, crosspost])
  • shouldVideoAutoplay: never (default: always)
  • shouldLoadAllComments: true (default: false)
top 4 comments
sorted by: hot top controversial new old
[–] kuro_neko@lemmy.ca 3 points 6 months ago

Hi, thank you for the report. I'm going to add a setting in the next release to control if keyword filters should be case insensitive or not. Cheers!

[–] sirxdaemon@lemmy.ca 1 points 6 months ago* (last edited 6 months ago) (1 children)

Currently it's filtering with case-sensitivity. So if you have "Trump" and a post title has "trump" then it won't be filtered. There certain situations where case sensitivity is helpful but I think generally, it's better to have it not be case sensitive.

[–] HypnoticSheep@lemmy.world 0 points 6 months ago (1 children)

The issue is that the case sensitivity is not working either. As I mentioned in the report, adding "trump, Trump" will not filter posts containing "Trump".

[–] sirxdaemon@lemmy.ca 2 points 6 months ago* (last edited 6 months ago)

When I was testing before, I only had one keyword and I didn't run into I think the problem you're having. The filter list is comma seperated but if you have a space after the commas then the word does not get filtered. It does get added to the list of keywords, which is confusing.

Also, if you add a word with a comma and a space before it, it's saved as a comma and two spaces in the filter text field; when you go back into the page.

EDIT: Maybe I should clarify things. So to fix any keywords not working, remove any spaces before the keyword. New keywords need to be comma separated but without a space. The list will save and show with spaces but that's the current formatting.