Tired of not knowing who was an Original Bird (OB)? Then this extension is for you! A green checkmark is added on Twitter to indicate who was an OB before the great purge of April 20th, 2023. Don’t believe your eyes? Go watch our YouTube video and read the FAQ!
Features
- Customize checkmark color, or replace with your OWN text / emoji / image!
- Shows checkmarks on embedded Tweets (e.g. on news websites).
- Toggle Twitter Blue checkmarks on/off.
- Displays green checkmarks next to legacy verified users.
Donations
Thank you to all of our generous donors and contributors! Please go check them out and show them some love!!!
If you like using this extension, then please consider donating to support this project!
Extension users will see all donor names in light orange and all contributor names in light purple on Twitter.
FAQ
How do you determine who was legacy verified?
Users will see a green checkmark beside OBs who were legacy verified before April 6th, 2023. This means that @verified followed them on Twitter at the time of data collection. We sourced our data from thansen0. Please show them some love!
Note: We are currently only comparing Twitter handles (because it would be costly to verify against the actual Twitter ID). We recognize that Twitter handles may have changed and will be working on it when we have the resources.
Why is my browser randomly visiting Elon Musk's Twitter page?
This is a normal operation to retrieve Twitter's checkmark that happens once on installation. Since Elon Musk owns Twitter, he is always verified and we obtain Twitter's checkmark from his page after installation. Our extension does not include any Twitter source code or assets to avoid copyright issues.
Why do I need to grant permission to access data on Twitter?
We access Twitter websites to read user handles in order to check if they are verified and write HTML to add checkmarks. We don't collect any user data. If you are concerned about privacy check out our privacy policy or install from our open source GitHub repository.
How do you keep your extension safe from security vulnerabilites?
Firstly, we use Github's CodeQL to run automatic scans on our entire codebase (including dependencies we use) for each iteration and before official releases.
Secondly, we are working on adding another layer of defense using DOMPurify to guard our checkmark HTML from cross-site scripting attacks. This is largely unnecessary since we retrieve our checkmark from twitter.com over HTTPS. Still, we want to be extra paranoid in case Twitter does something unexpected.
Lastly, we ask contributors on our GitHub repo to report security vulnerabilities in private so that we have a chance to create a patch. See our security policy.
Can I be added to the legacy verified list?
No. (For legacy verified users, please see below.)
As of right now we're only planning on this to be a static list (like a Wayback Machine). If we were to implement our own user verification then it would require volunteers or some external funding, which would 100% draw the ire of Twitter.
Of course, you can always donate to us at the link above and get recognition! (Just be sure to give us your Twitter handle.)
I'm a legacy verified user and I don't have a green checkmark. Can I be added?
Please first read the instructions here.
If you believe you have sufficient proof, then send us an email. Do not create a GitHub issue in this case. For bugs, please see below.
I found a bug. How do I report it?
Please first read the contributing guidelines.
Twitter can change its website on us anytime so don't hesitate to create an issue on GitHub if checkmarks are missing! You can of course reach out to us at our email listed on the Chrome Web Store. However, for sanity purposes we request you stick to GitHub issues.
How do I become a contributor?
Always consult the contributing guidelines first and then make a GitHub issue. Remember to include your Twitter handle when you make your pull request. If it gets approved, then congrats, you're a contributor!
(Discord for donors and contributors coming soon.)
Privacy
We take your privacy seriously and do not collect any user data. We will always be transparent and open source.
For more information please see our Privacy Policy.