Just checking in since this is turning out to be a big update, especially for a single point release. These are the changes implemented thus far. I thought I was ready for a feature freeze, but as I've implemented these, some things have become redundant so I've had to double back and find a way to combine them (e.g. merging community tagging and community groups into one feature).
Highlights:
The filtering system has been further expanded to include URL domains and entire instances. Community groups have been overhauled and can now have filter policies applied to their member communities. User tagging has been implemented, and those tags can be used in filter policies as well. You no longer need to be logged in to utilize community groups, favorites, or user tagging. This means you can completely curate your experience without even having to log in!
General
- Lots of bugfixes
- Re-implemented the auth and profile library and initial login flow
- Small UI tweaks and refinements
- [Planned, not implemented yet] Suppress notifications for filtered items
- [Planned, not implemented yet] Allow muting replies for posts and comments
- [Planned, not implemented yet] Revamp settings page
Filtering is much more granular
- You can optionally completely hide posts and comments that match any of your filters (instead of showing the placeholder)
- Users of blocked instances can be completely hidden (posts and comments) if you wish.
- Can now filter posts by URL domains (e.g. if you don't want to see any posts linking to example.com, add that to your filter)
- Can define wildcard domains (*.example.com) such that
anything.example.com
will match the filter - Built-in toggles for Bluesky, Facebook, Reddit, and Twitter/X so you don't have to manually enter each of their multiple domains
- Can define wildcard domains (*.example.com) such that
Limited (but growing) Built-in Spam Detection (and filtering)
- Detected spam posts and comments are hidden and can be revealed
- Domains that are commonly spammed by bona-fide spam accounts will trigger the filter
- Brand new accounts linking to blogspot [dot] com will be hidden and flagged as blogspam. This can be applied for other domains, too, but blogspot is the one that's typically spammed. Blogspot links will not always be flagged, just if they're posted from brand new accounts.
- You can optionally filter out "help farmer" posts. Help farmers are those accounts that spin up a disposable alt, throw out their question in one of the various "ask" or support communities, and then delete the post and account shortly thereafter and taking any answers and discussions with them. I HATE those people. The only way to really deal with it is to stop interacting. So now you can filter those posts and optionally completely hide them.
Community Groups Got a Big Upgrade
- Community groups now (also) act like Community Tagging. Any groups a community is a member of will be shown as flairs (it's on by default but you can turn it off).
- The group list in the sidebar/navbar is now searchable.
- Community groups can be turned into filter groups (see more below).
- The community details are no longer stored which reduces localStorage usage
- The community groups have been moved out of the profile and are now system-level.
- Sadly, this means that you can no longer have separate groups for each profile. I thought about making the new groups profile-specific, but decided against it.
- Groups are now able to be used without being logged in
- I'm debating on including a default set of community groups if there are no user-defined ones. Haven't decided yet
- Groups can now be exported/imported separately (and merged). This allows you to share your groups with others.
Community Groups Can Be Used as Filter Groups
- Turn any community group into a filter group (or vice-versa)
- Filter groups can be listed and searched separately in the sidebar
- Filtering rules can be defined (and combined) that apply only to communities that are a member of that group:
- Filter all posts to any of those communities.
- Filter users with certain tags in those communities
- Filter specific keywords only in those communities
- Filter users of specific instances only in those communities
- Filter URL domains only in those communities
- Filter (collapse) or completely hide any items which trigger the filter
Community Filter Group Examples
There's someone who posts good stuff in some communities but they make cringe-worthy memes you don't want to see. Also, you don't want to see any memes linked/crossposted from lemmy.ml.
Solution:
- Add your meme communities to a group. We'll call it "Memes". Enable the filter group option.
- Tag anyone who makes terrible memes with the "Y Ur Memes No Good Tag" (or a tag of your choosing)
- Add the tag "Y Ur Memes No Good" to the filter list in the "Memes" community group.
- Add
lemmy.ml
to the domain filter list in the "Memes" group. - Add
lemmy.ml
to the instance filter list in the "Memes" group if you also don 't want to see any memes posted by a user there. - Optionally completely hide those submissions
- Enjoy less terrible memes in your feed while still seeing content from those users elsewhere.
You like to stay up to date with current events, but certain topics or people constantly overwhelm the community
Solution:
- Add your news and/or politics communities to a group and enable the switch to use it as a filter group.
- Add any keywords for overexposed topics or people to the "Keywords" filter list
- Recommended: Do not completely hide the keyword matches and let them remain as the placeholder / stub posts which will let you tune your keywords.
- Once your keywords are tuned sufficiently, optionally completely hide the matches.
Screenshots:
Group Editor:
Filtered "Help Farmer" Post:
Community Group Tagging:
Community Group Filtering: