This addon became broken when Twitter changed domain names, but Mozilla has been blocking updates to this addon the entire summer. Twitter is unusable without this addon; please allow them to push an update through this time
1 Like
Cross-referencing against the Blue-Blocker-side issue:
Iām thinking if we could get PR 328 merged, that might help, but it could use some work:
But yeah, regardless of whether that gets merged or not, updates really ought to get approved in the future.
2 Likes
They already did that, but firefox reviewers just keep finding silly things to block updates for
Other addon supposedly are being victimized as well
@paisleyport, with respect, the issue you linked is a build reproduction failure, meaning that the source code and build steps provided did not produce an output matching the extension submitted by the developer. For reviewers, thatās a minimum bar to meaningfully assess the risks posed by an extension.
I know the review process can be frustrating, but at the end of the day weāre all just trying to make usersā lives a little better.
@dotproto, with respect, this is the 3rd build thatās been rejected, each build has been rejected for a different reason; its been getting hard to believe āweāre all just trying to make usersā lives a little better.ā from a userās perspective.
1 Like
Itās totally normal to get rejected multiple times in a row 
, we all went through that and more.
Note that it could be much worse, for example Safari store would reject you for a screenshot that shows a donation button on your own homepage.
Regarding the reproducing the build - this is one of the most common issues here and itās the one thatās most important.
If you are using NPM, make sure to upload also package-lock.json file and maybe instead of npm i use npm ci
Just to bring this back up here:
Please approve an update on here. This add-on has been broken for ages, and every built has been rejected for different reasons, inlcuding the reviewer not seeing that there was a privacy policy on the mozilla add-on store.
I understand there is a new version that fixed the built reproduction failure you refer to above, but it appears to be stuck in a queue awaiting approval. As the add-on is currently not functional the repeated rejections on different grounds each time are really frustrating, so it would be good to see some movement in the approvals process
Thank you in advance!
EDIT to add: there have been at least 8 versions that have been rejected, with the 9th currently under review. Some of the rejected versions only change was dealing with the comments by the reviewer, and the newer version was rejected by the reviewers for a different reason. This is asking too much of the people working to keep the add-on safe and functional, so please approve the add-on (I donāt even care which version, as long as it fixes the url issue) and consider if all the requirements being used are actually necessary.