AkkomaGang/akkoma-fe

Fork 72

[feat] Indicate search results were hidden by the wordfilter #271

New issue

Closed

opened 2023-01-06 14:23:44 +00:00 by catgirl · 1 comment

catgirl commented

2023-01-06 14:23:44 +00:00

The idea

When a user searches for a post, and one is found but hidden by their wordfilter, give some indication that this is happening.

Suggestion: add a message to the detail pane saying "Results are hidden due to filter preferences"

The reasoning

When a search returns a post that is hidden by the wordfilter, the following happens:

the search results UI header shows "Posts (1)"
the post doesn't appear in the results; that is, the detail pane below the header is empty
there is no indication that the post was intentionally hidden

This is confusing.

It wasn't until I saw the header showing there were results and opened the dev tools to see that the search request was returning the post that I realised what was happening. Prior to this, I'd assumed there was some bug, or federation problem.

I think this improvement would give a clear indication that, in the case of intentionally searching for a post, the instance does actually have it, but that it was the user's preferences that caused it not to be accessible.

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 When a user searches for a post, and one is found but hidden by their wordfilter, give some indication that this is happening. Suggestion: add a message to the detail pane saying "Results are hidden due to filter preferences" ### The reasoning When a search returns a post that is hidden by the wordfilter, the following happens: - the search results UI header shows "Posts (1)" - the post doesn't appear in the results; that is, the detail pane below the header is empty - there is no indication that the post was intentionally hidden This is confusing. It wasn't until I saw the header showing there _were_ results and opened the dev tools to see that the search request _was_ returning the post that I realised what was happening. Prior to this, I'd assumed there was some bug, or federation problem. I think this improvement would give a clear indication that, in the case of intentionally searching for a post, the instance _does_ actually have it, but that it was the _user's_ preferences that caused it not to be accessible. ### 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.

2023-01-06-062203_644x291_scrot.png

54 KiB

2023-01-06-062251_1017x224_scrot.png

63 KiB

Mergan added the

Feature request

label

2023-02-01 07:28:20 +00:00

Oneric commented

2025-10-15 19:55:35 +00:00

Owner

This already happens (now at least; idk if it already did when this was filed), though I think there’s a config option to fully remove rather than just hide filtered posts in which case not showing anything is expected

This already happens *(now at least; idk if it already did when this was filed)*, though I think there’s a config option to fully remove rather than just hide filtered posts in which case not showing anything is expected

Oneric closed this issue

2025-10-15 19:55:35 +00:00

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

AkkomaGang/akkoma-fe#271

No description provided.

Rows
Columns