GoodTwitter Beta is a productivity chrome extension. it's a free extension , it has 673 active users since released its first version, it earns an average rating of 4.38 from 8 rated user, last update is 1665 days ago.
THIS IS THE BETA VERSION OF GOODTWITTER This is a version of GoodTwitter that contains some bugfixes that might be unstable. If you want to try this version UNINSTALL REGULAR GOODTWITTER FIRST! This Add-on brings back old twitter by changing the user agent of all your browsers requests to the one of an older browser For troubleshooting go here https://github.com/ZusorCode/GoodTwitterChrome/blob/master/troubleshooting.md This project is open-source: github.com/ZusorCode/GoodTwitterChrome Want to support me? ko-fi.com/zusordev Built by Zusor inspired by super raging about the redesign
You could download the latest version crx file or older version files and install it.
English.
60% user give 5-star rating, 20% user give 4-star rating, 20% user give 1-star rating. Read reviews of goodtwitter beta
You could find more help information from goodtwitter beta support page.
You could send emails to publisher, or check publisher's website.
More about manifest_file of goodtwitter beta.
You could click to report abuse of goodtwitter beta.
1. "This browser is no longer supported" every time I open Twitter after installing this 2. Doesn't solve the problem I wanted to fix: where twitter feed jumps around randomly as I scroll down.
Doesn't work for me! :((( why?
Great, great extension BUT I noticed last night (while on my desktop) that I'm not seeing a "1" on top of "Messages" anymore when I have a new direct message. I have GoodTwitter Beta on my laptop at home and GoodTwitter on my work desktop and I'm not seeing the # indicator on messages when I have a new one with either extension. I've signed out and back in. I've removed the extension and added it back and I've tried different browsers. To make sure it wasn't an issue with my Twitter account, I tried regular Twitter without the extension and the number does appear there, so this issue is with the extension.