Skip to content

Extension Removed from Chrome Web Store #95

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

Open
ThatBlockyPenguin opened this issue Mar 16, 2025 · 3 comments
Open

Extension Removed from Chrome Web Store #95

ThatBlockyPenguin opened this issue Mar 16, 2025 · 3 comments

Comments

@ThatBlockyPenguin
Copy link

Image

Exactly the title. Is there any way to undo this - I greatly value this extension, thanks to all who work on it!

@d-513
Copy link
Member

d-513 commented Mar 18, 2025

Google changed the way extensions like this that block certain content work with Manifest V3. Initially it would have killed the extension entirely but now I see they softened the limits a bit so it could theoretically still work but need to be rewritten. Since the StopModReposts project is in low-maintenance mode I'm not sure if I will do that but if it's very useful to you I will consider it. Another alternative is to use the Firefox extension as that one still works as far as I know.

@ThatBlockyPenguin
Copy link
Author

Hey, thanks for the response!
I would be in no way opposed to a new Chrome version - but absolutely don't feel pressured! I am in all honesty considering moving to Firefox anyway (in fact I currently have both installed as I evaluate what the pros and cons are of moving), so if I do switch I'll just go with that one.
Thanks again!

@Brandonbr1
Copy link
Contributor

Google changed the way extensions like this that block certain content work with Manifest V3. Initially it would have killed the extension entirely but now I see they softened the limits a bit so it could theoretically still work but need to be rewritten. Since the StopModReposts project is in low-maintenance mode I'm not sure if I will do that but if it's very useful to you I will consider it. Another alternative is to use the Firefox extension as that one still works as far as I know.

I managed to get it working by just changing the manifest.json to v3 support capabilities. It does not seem to be causing issues.

My version can be found at: Brandonbr1@0e3fd2a

However, I could very well be wrong.

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

No branches or pull requests

3 participants