You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have recently filtered some repetitive posts via the mute hashtag button but found that I could still see the hashtag as I scrolled.
When I investigated the filter in setting it appears that even though I was attempting to mute the tag while in the "Federated" feed, the new filter was only being applied to the "Home" feed. I think this is counterintuitive, if I mute a hashtag that I saw on a different feed I would expect it to be filtered in that feed at a minimum, but instead it filters it in a feed I'm not looking at.
Can the behaviour be modified to have the new filter apply to all tabs or at a minimum to the tab the hashtag was viewed from?
Tusky Version: 24.1
Android Version: 11
Android Device: I don't think this is device specific?
Mastodon instance (if applicable): N/A
I searched or browsed the repo’s other issues to ensure this is not a duplicate.
The text was updated successfully, but these errors were encountered:
I have recently filtered some repetitive posts via the mute hashtag button but found that I could still see the hashtag as I scrolled.
When I investigated the filter in setting it appears that even though I was attempting to mute the tag while in the "Federated" feed, the new filter was only being applied to the "Home" feed. I think this is counterintuitive, if I mute a hashtag that I saw on a different feed I would expect it to be filtered in that feed at a minimum, but instead it filters it in a feed I'm not looking at.
Can the behaviour be modified to have the new filter apply to all tabs or at a minimum to the tab the hashtag was viewed from?
Tusky Version: 24.1
Android Version: 11
Android Device: I don't think this is device specific?
Mastodon instance (if applicable): N/A
I searched or browsed the repo’s other issues to ensure this is not a duplicate.
The text was updated successfully, but these errors were encountered: