Previous updates about this:
bsky.app/profile/chro...
bsky.app/profile/chro...
bsky.app/profile/chro...
bsky.app/profile/zmya...
@chromevoiceactions.bsky.social
Control Chrome, manage your tabs, and look up websites, maps, directions, music, and more with spoken commands Β· Created by @ZMYaro.com π chromewebstore.google.com/detail/hhpjefokaphndbbidpehikcjhldaklje π§βπ» github.com/ZMYaro/chrome-voice-actions
Previous updates about this:
bsky.app/profile/chro...
bsky.app/profile/chro...
bsky.app/profile/chro...
bsky.app/profile/zmya...
To reiterate: Older Chromebooks won't run βMV3β extensions, so Google is trying to force developers like me to switch to an extension format that will force people who use older Chromebooks to buy whole new ones! Brave, Edge, Firefox, Opera, and others support MV2 alongside MV3.
(3/3)
You generally shouldn't touch chrome://flags unless you know what you are doing, so it is ridiculous this is the only way to keep using βMV2β extensions. Please be skeptical and tread carefully whenever someone tells you to open chrome://flags!
(2/3)
Update: It appears you *CAN* still use βmanifest version 2β extensions in new versions of Chrome:
1. Go to βchrome://flagsβ.
2. Search for βMV2β.
3. Disable the βDeprecation Stageβ flags, and enable βAllow legacy extension manifest versionsβ.
4. Close and relaunch Chrome.
(1/3)
If you recently updated Chrome, you may have found yourself unable to use Voice Actions for Chrome due to Google's βmanifest version 3β policy. I am working on an MV3-compatible version of Voice Actions. In the meantime, it still works in Brave, Edge, Opera, and others.
23.06.2025 03:53 β π 1 π 1 π¬ 0 π 1Apparently Google finally fully forcibly disabled βmanifest version 2β extensions (including Pushbullet and @chromevoiceactions.bsky.social), and I guess that was the push I needed to finally ditch #GoogleChrome as my primary browser π Heck, even #MicrosoftEdge still supports MV2 rn!
21.06.2025 20:45 β π 1 π 1 π¬ 0 π 0For more about what Google is doing, see my previous thread: bsky.app/profile/zmya...
You can also read Mozilla's statement:
blog.mozilla.org/en/products/...
(8/8)
β» When installed, Extensions settings β Voice Actions for Chrome β Details β View in Chrome Web Store takes you to the official Voice Actions for Chrome page on the Chrome Web Store.
(7/8)
β» In βDeveloper modeβ, the extension's ID (hhpjefokaphndbbidpehikcjhldaklje) appears in the URL of the official Voice Actions for Chrome page on the Chrome Web Store.
(6/8)
β» It comes from the official Voice Actions for Chrome project on GitHub, which is linked from the official pages on the Chrome Web Store page and social media.
β» When installed, Chrome *DOESN'T* warn about it being corrupted or unable to verify with the Chrome Web Store.
(5/8)
You should be wary of any instruction to install an extension this way. It is a serious safety risk that this seems the most reliable way to install βMV2β extensions in the newest version of Chrome. You can increase your trust in this Voice Actions for Chrome extension file by noting:
(4/8)
4. Open the folder you downloaded the CRX file to.
5. Drag the CRX file from your downloads folder to the extension list on chrome://extensions.
6. Confirm you want to install the extension.
7. When you are done, go back to chrome://extensions and turn off βDeveloper modeβ.
(3/8)
1. Download the CRX extension file from the Voice Actions for Chrome project on GitHub: github.com/ZMYaro/chrom...
2. Open Chrome Extensions settings (chrome://extensions).
3. Use the switch at the top-right corner to turn on βDeveloper modeβ.
(2/8)
Update on this:
Google is now disabling the install button in the Chrome Web Store for some people. If that happens to you, you can still install Voice Actions for Chrome; they just make it more of a pain.
These are the steps to follow now:
(1/8)
A panel in Chrome extension settings says, These extensions were turned off because they're no longer supported. Chrome recommends that you remove them. Learn more about supported extensions. The list includes Touch-Friendliness for Discord, Voice Actions for Chrome, and XKCD Hover Text. Select More actions β Keep for now.
A confirmation dialog says, Keep Voice Actions for Chrome? This extension is no longer supported. Chrome recommends that you remove it instead. Select Keep.
I am going to keep @chromevoiceactions.bsky.social and my other extensions on MV2 and test them on older Chromebooks for as long as Google lets me, and when Chrome tries to disable them, you manually reenable them at chrome://extensions. I hope this thread helps; thank you for understanding! (5/5)
03.03.2025 19:37 β π 1 π 1 π¬ 0 π 0If you have been getting warnings from Chrome that Voice Actions for Chrome is βno longer supportedβ, don't fret!
*Voice Actions for Chrome is still supported, and you can still use it!*
Here's what's going on:
A panel in Chrome extension settings says, These extensions were turned off because they're no longer supported. Chrome recommends that you remove them. Learn more about supported extensions. The list includes Touch-Friendliness for Discord, Voice Actions for Chrome, and XKCD Hover Text. Select More actions β Keep for now.
A confirmation dialog says, Keep Voice Actions for Chrome? This extension is no longer supported. Chrome recommends that you remove it instead. Select Keep.
Google Chrome has started telling people several of my extensions, including @chromevoiceactions.bsky.social, are βno longer supportedβ.
**This is extremely misleadingβI still support them, and you can still use them!**
This is Google trying to force extension developers' hands:
(1/5)
Hello Bluesky! Sorry to be joining you under such circumstances, but great to be here nonetheless!
03.03.2025 19:44 β π 2 π 0 π¬ 0 π 0