Okay, sorry, yes, my answer was a bit closed minded. We are reviewing the ratings limits taking those usage into account too.
I get it. We’ll do our best is all I can say.
Some people complain before doing that effort. I’m prefer asking the question before assuming your intent. 300 is not 3000. Maybe some of them would be better as a “Favorite per year” feature, maybe some of them are just archive (we could have a limit for private and public lists), maybe some of them could be lighter lists that are just used by some integrations,… I’m not asking questions to bother you, I’m trying to see if we can improve your experience in any meaningful way.
I disagree on two things here: first, I do help on V3. Second, I’m Product Manager for Trakt. If I can improve your experience on Trakt without being a V3 thing per-se, I’ll do it because the impact will be bigger on every Trakt frontend.
That’s okay. I’m still not getting the whole picture. Maybe this is something that can be done with the API and custom filters? Maybe we need to add filters that would help?
That’s a really good point, and today, with Rippple, I’m heavily using filters for everything. That’s a reason why those new limits take “Dynamic Lists” into account. We’d like to avoid those kind of lists going forward. If it can be done with a filter, that’s better for everybody!