-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
Did the plug-in author take the initiative to remove the plug-in from Firefox or did Firefox take the initiative to remove the plug-in? #755
Comments
Mozilla removed it |
Many other Chromium based browsers have already made changes to continue the old manifest version, such as Vivaldi. I can confirm that OldTwitter works on Vivaldi as well. |
However, how to keep using the extension in Firefox? Plus, why is the issue closed? |
Because the author has already answered it (please open the "Discussion" interface). I asked this question because this interface was not open (I saw it later, so I marked this question as "closed"). If you installed the add-on on Firefox before it was removed, please do not do anything. If you want to continue using the plug-in after it is removed, you need to switch Firefox from the official version channel to any one of the three channels: ESR, Nightly, and DEV. Or switch to browsers that are based on Chromium but still support manifest V2. |
Regarding the countdown to the activation of V3, if the browser you are using has clearly "no longer supports V2", and your browser plug-in will be wiped out due to the new standard. You need to migrate as soon as possible. (The UBlock Origin, Tamper Monkey, and CanvasBlocker I use will be wiped out by the new standard) (Firefox retains support for V2 while also adding support for V3) |
OldTwitter supports Manifest v3, it should work on any Chromium browsers |
When I wanted to install this plug-in, I found the following prompt on the Firefox store website:
**_If you’ve followed a link from another site for an extension or theme, that item is no longer available. This could be because:
So is it the first case or the second case? I don't want to be forced to change browsers because of using this plug-in (since Google is about to implement the manifest v3 standard, the browser plug-ins I use will be completely broken by this standard. So I can only use Firefox)
Hope to get a reply, thank you.
The text was updated successfully, but these errors were encountered: