Can't install Chrome extension anymore (Manifest V3)
๐ bug report
โ๏ธ Description
If you go to the Chrome extension page, you can't get the extension anymore, most probably because it's not updated with the new Manifest V3.
๐ต๐ผโโ๏ธ Is this a regression?
yes
๐ฌ Minimal Reproduction
- Use Chrome Browser (from Edge, you get a warning but you are still able to install it)
- got to chrome extension page
- the plugin is not available anymore
๐ Your Environment
Chrome browser
๐ฅ Exception or Error or Screenshot
๐จ Urgent Attention Needed: Manifest Compliance and Security Concerns
โSecurity isn't optional โ it's fundamental.โ
โ Problem Statement
The current version of this project appears to not comply with the latest Google security standards, particularly concerning the Chrome Manifest updates. This issue stems from the use of deprecated manifests, which Google has clearly marked for review and updating.
Unfortunately, it seems this concern has been overlooked or ignored, despite likely communications and reminders from Google.
โ ๏ธ Consequences of Inaction
- โ Loss of Trust: Users lose confidence in the platform when they encounter warnings or blocked extensions/apps due to security violations.
- ๐ Reduced Accessibility: With Chrome revoking support, users are also less likely to trust or use the product on other platforms.
- ๐งจ Brand Damage: Failing to meet modern security standards can severely impact the reputation and reliability of the project.
- ๐ช Missed Notifications: Ignoring Google's mails and alerts further implies a lack of active maintenance, which is a red flag for users and contributors alike.
โ Suggested Action Plan
๐ 1. Update the Manifest
Ensure the project complies with the latest Manifest v3 requirements. This includes:
- Upgrading permissions and background script handling.
- Ensuring all APIs used are still supported.
- Fixing any deprecated features or flags.
๐ต๏ธ 2. Audit Security Practices
Perform a security audit:
- Check third-party dependencies.
- Validate data-handling logic.
- Follow Googleโs Extension Security Checklist.
๐ฌ 3. Monitor and Respond to Google Alerts
Set up a watch mechanism for:
- Emails from Google Developer accounts.
- Official documentation updates.
- Community discussions on extension compliance.
๐ค Why This Matters
Your project has a strong following and user base. Neglecting fundamental updates like these undermines years of hard work and trust. It's not just a technical issue โ it's a credibility issue.
Users need to feel safe, contributors want to see responsiveness, and platforms demand compliance.
Letโs make sure this project keeps shining ๐ โ not fading away due to preventable missteps.
๐ Conclusion
Act now.
Letโs fix the manifest. Secure the platform.
Regain trust โ and grow stronger than before.
Security is not a one-time feature โ itโs a continuous commitment.
๐ Authored by a concerned contributor who cares deeply about the projectโs future and its community.
the above comment its definitely made by AI
I wanted to try Responsively to see how it works and if i can add it to my work flow but I noticed that I can't install chrome extensions. In chrome itself i have been using automa to hold dummy login credentials so i don't need to manually copy and paste each dummy accounts. Unless there are other extensions out there for this kind of task. I think this could be worked around by using the responsively helper extension while keeping automa in my actual chrome browser but responsively help can't be installed in responsively.