For example, if you're ok with ecchi, harem, and school anime, but don't like high school ecchi harem romcoms, you could exclude an "ecchi," "harem," and "school" genre combination.
That seems very specific. Not only do I not really see the point, it would complicate the filters for little benefit, leading to even poorer performance site-wide, so I'd rather not even try.
So are you telling me that having an exclusion list hurts site performance, and if we get rid of it, performance will improve, and will the same happen if the exclusion list is only for a select set of users?
@Teasday
Ah, if it affects site performance... RIP. Don't suppose there's some better way to do it with a user-side script?
It's pretty common for people to search while using and excluding multiple genre tags. I'd assume wanting to have certain combinations always filtered would also be useful. When you put two or more genres together, it does become a different thing entirely. Like a "Seinen" + "Smut" genre combination would be very different from an "Josei" + "Smut" combination, as well as very different from your Seinen or Josei without smut.
So are you telling me that having an exclusion list hurts site performance, and if we get rid of it, performance will improve, and will the same happen if the exclusion list is only for a select set of users?
Because of how results caching and retrieval is implemented right now, yeah kind of but not by a lot. All kinds of filters making caching more difficult, some more than others. The simple and/or tag exclusion that we have right now is much, much more straightforward than a set of complex tag exclusion rules would be.
Ah, if it affects site performance... RIP. Don't suppose there's some better way to do it with a user-side script?
It's pretty common for people to search while using and excluding multiple genre tags. I'd assume wanting to have certain combinations always filtered would also be useful. When you put two or more genres together, it does become a different thing entirely. Like a "Seinen" + "Smut" genre combination would be very different from an "Josei" + "Smut" combination, as well as very different from your Seinen or Josei without smut.
Hiding things client-side is of course free for the server but it comes with some problems of its own. Also, I don't even want to think about what kind of a UI solution this feature would require, especially for a feature that I doubt is particularly vital.
Seinen and Josei aren't (at least currently) tags, but I get your point. With our current situation, I just find it difficult to justify the benefits vs. potential performance impact and development time.