Filter by account

Environment

• Installation type:
  • OTP
  • From source
• Pleroma version: 2.0.6-stable
• Operating system: (Docker) alpine:latest
• PostgreSQL version (postgres -V): 11.x

Bug description

Mastodon-FE filters do not take author into account when filtering. If I'd like to filter '@user@foo.bar' from the Home TL (or similar with filters available) the filter rules will NOT match on author (or any other fields that aren't the main post). This makes it impossible to filter users from TL's that are also in lists.

Proposed: have an ability to filter by author / poster so users can be filtered from individual TLs

How is this different from a mute? I think I misunderstand what the goal is here, sorry!

I don't want the account muted globally, just in a specific timeline (my Home TL in particular).

I have the user(s) in other lists and want them filtered from the Home TL to help keep my Home TL more on point and less of a 'firehose'.

If I add the user to the filters on the Home TL it's not filtering on the user id (@foo@bar.baz for example) and I'm still seeing their posts.

By filters do you mean the regex on the home timeline or "Mastodon Filters™" (which we don't really have an interface for yet)?

The regex on the Home TL

moved from pleroma#1871 (moved)

Moved to MastoFE then as it's done there.

Also regex filter will only match against the post content so it can only filter mentions. Could you give an example of the regex that you're using? I think it should be something like user@domain\.tld as the @ for mention might not match because of the HTML formatting.

I'm currently using @user@domain.tld for the matches and I was hoping to be able to match on the author attribute of a post instead of the content.

Is that something that could be setup as a possible feature for a future update?

Not really, there is muting a user but that works for the whole feed and IIRC pleroma-fe is the only one which allows to have muted posts/notifications be collapsed on one line.

The reason for this is mostly because MastoFE is a distribution of Glitch-Soc's frontend and has no developers working on it (I basically only package it).