@abucci@anthony.buc.ci Don’t we have enough tools that allow users of single-user and multi-user pods to block stuff they don’t want to see? 🤔 The list includes:

• Unfollow a feed
  
• Mute a feed
  
• Mute a twt
  
• Mute a yarn

@prologic@twtxt.net add mute by language. 😊

@bender@twtxt.net As discussed on IRC, I think what you really want is per-User level filters. The question is what? Keyword/Pattern based? Language? Anything more? 🤔 I consider “Muting” and “Filters” to be somewhat different I guess… If I had to define it:

• Filtering is content based
  
• Muting is source based (feed, twt or yarn)

And if I were to build this, I would simply extend the User.Filter() function such that:

• Source based filters (mute) is the first path
  

Followed by:

• Content-based filters (keyword, language, etc)
  

And of course we’d have to build a fancy UI around this 😅

@prologic@twtxt.net pattern based filtering can get quite expensive, no? If not, then it would be nice to have, of course. And, as I wrote before, language.

@bender@twtxt.net probably no more expensive than keyword based filtering to be honest. Right now it’s O(n) complexity. It would probably be worth caching “filtered per-user views” (including the timeline) some of which we don’t do right now. It would probably save a few % points of cpu utilisation of a larger pod.