Getting closer!
Differences since Beta 1: The updated filtering capabilities have been merged in. I hadn't originally planned to spruce up the filtering in this release, but it was born out of necessity. That said, I'm quite happy with the refinements that have been made.
As before, I need the extra eyes on this to suss out any last minute bugs. Hopefully no more features creep into this release. This one was an exception as I just...needed it.
If you find any bugs, please let me know: Reply/post here, Github issue, report it in the Matrix rooms, wrap a note around a brick, you know the drill.
Change Notes for Filtering System
Filtering Revamp
The filtering subsystem has been refactored and enhanced. Prior to this release, anything that was filtered was simply discarded before being rendered.
Now, filtered objects will show a placeholder that indicates which filter was triggered (or which keywords triggered the filter). Clicking the "eye" button on the placeholder will show the hidden content.
This is the case for both posts and comments that are hidden by your filter preferences.
Notes on Filtering
There are a few safety checks in place that will disable the filters under certain conditions. The first two are to prevent moderation blind spots, and the rest are just sanity checks/compromises to keep from over-complicating things.
- If you are a moderator, the filters will not apply to content posted to any community you moderate. This includes viewing reports.
- If you are an instance admin, the filters will not apply to content posted to any local communities.
- The filters will not apply when viewing your own content anywhere in the app.
- Filters are not applied when viewing someone's profile.
- If you have a community filtered, going to its
/c/
page or browsing it in a modal will show the community's content, though any other filters are still applied (keywords, user filters, etc). Reason being, you went to the commmunity, so the content shouldn't be filtered out by default.
Finally, filters are global and apply to all accounts in use in the app. You cannot have different filters on one account than on another. I may change my mind at some point, but it made much more sense to have one set than one set per profile. It also eliminates the need to have extra management tools to copy them or sync them between profiles and other things like that.
Keyword Filters Now Apply to Comments
Keyword filters now apply to comments! I had always meant to apply them there, but until the work done to the comment section in this release, I didn't have a way to apply them that wouldn't nuke the rest of the thread. Now, just the offending comments will be hidden with the rest of the chain remaining intact.
Filtered comments will hide the score and creator as well. Unless manually revealed, the "creator" will be [email protected]
with the Tesseract logo as the avatar. Revealing the comment will replace that with the actual creator. This is to both further hide/mask content you don't want to see as well as keep the formatting/rendering consistent.
Additional Filtering Options
There are a few new filters available as of this release:
Hide Content from Blank Profiles
A "blank profile" is one that lacks both a bio and an avatar. Why? Sometimes you might want to filter out "faceless opinions" for a while and/or only deal with the people who are more likely to be here for the community rather than anonymous opinion shouting.
Filter Users (Soft Blocking)
You can now filter users rather than blocking them. This is especially helpful for those who moderate large communities. Think of filtering out a user like a "soft block".
Why would you want to filter a user rather than block them?
Lemmy's blocking has a couple of glaring issues:
-
Content from blocked accounts does not show up in communities you moderate. This leaves a huge blind spot when you don't want to see content from certain users but it is not warranted to ban them from your communities.
-
When you block a user, not only are their comments not visible in the comment section, you will not see any replies to them, either. Depending on who you block, this could cause you to miss out on quite a bit of discussion.
If you filter those users instead, both of those are addressed:
-
Filters are automatically disabled on communities you moderate, so you will still see content from the filtered users there but you won't anywhere else.
-
Only the filtered user's comment will be masked; all the replies will be visible.
How to Use:
To filter (or un-filter) a user, click their username to bring up the User Profile Modal. From there, use the "Filter User..." (or Un-Filter User...) button in the modal. When a user is filtered, all of their content in the current area will collapse to a placeholder (or un-collapse if you're un-filtering them).
You can also manage the filtered users direclty from Settings->Filters->User Filters
. Be aware that is pretty low-level, and you're basically editing a list of actor IDs. It's best to only use that to remove items, though you can add them there as well. It will also accept a comma-delimited list of actor IDs, so you can add them in bulk:
e.g.
https://instance.xyz/u/jerk1, https://instance.xyz/u/jerk2, https://other-instance.abc/u/AnotherJerk
Again, the users you enter directly must be in the actor ID format as that is what's compared when running the filters. An incorrectly formatted entry will not break anything, but it won't work, either.
Filter Communities (Soft Block Communities)
Similar to users, you can also filter/soft block communities.
Why would you want to do this instead of block the community?
Think of it like a soft unsubscribe. Need a break from a community but don't want to unsubscribe completely? Filter it! You'll see a placeholder stub in the feed for it, and you can reveal if you want to. Otherwise, it's out of sight, out of mind. When you're ready to get back into the community, just un-filter it.
The process is the same as with filtering a user, except it's accessed from the Community modal (click any community link in the app).

Another question: Are the button labels "Filter User" and "Filter Community" confusing?
Would it make more sense to call those buttons "Ignore User" and "Ignore Community"?
To me at least, "ignore" implies a server level block of some kind that would be consistent across clients.
Hmmm. Yeah, I can see that. I guess "filter" is fine.