Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loosely considering excluding the MV3 extension from 2 of my lists #994

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

DandelionSprout
Copy link
Member

So, well, it's not exactly a secret that I'm hostile to the overall concept of MV3, and have been for around 3 years by now.

So I've gradually and loosely thought about excluding 2 more of my lists from AG's dedicated MV3 extension, presuming people would chip in with their views on it. If the consensus would end up as "It'd be ridiculous to exclude regional lists from the MV3 extension" or similar wordings, then I'd accept such a verdict.

@DandelionSprout DandelionSprout changed the title Considering excluding the MV3 extension from 2 of my lists Loosely considering excluding the MV3 extension from 2 of my lists Aug 28, 2024
@ameshkov
Copy link
Member

Hi! I think if you really don't want to maintain it for MV3 this is completely understandable as it's at least a "one more thing to do".

The problem is that we'll still need to somehow make it work for Norwegian/Serbian/Croatian users that are using Chrome.

What do you think about a compromise like this: if the user report is from Chrome MV3 and it is really specific to MV3 then it's just handled on our side in FiltersRegistry?

@DandelionSprout
Copy link
Member Author

Sounds good enough to me. 🌞

@Alex-302
Copy link
Member

So leave it as is - don't exclude the filter?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants