Zusor · @ZusorOW
25th Jul 2019 from TwitLonger
GoodTwitter does not read your browsing history (explained)
A few people have been concerned by GoodTwitter in chrome asking for their browsing history on install. https://i.imgur.com/X7Gi1Vw.png . It doesn't actually read your browsing history, so here's an explanation why it asks for those perms.
When you install GoodTwitter in chrome, it clears your browsers cache for twitter then reloads it to make the user agent change actually do something. This isn't technically required, however you would have to reload the page yourself multiple times to clear the cache at which some users just thought the extension didn't work and uninstalled it.
So here's the code that does this:
chrome.browsingData.remove({"origins": ["https://twitter.com"]}, {"cacheStorage": true, "cache": true});
The name for the API is indeed browsingData which is why Chrome reports it as reading your history. If you still don't trust me, the code for GoodTwitter is open-source https://github.com/ZusorCode/GoodTwitterChrome.
Sorry if this was a bit rambly or confusing. If you have any questions, email me at goodtwitteraddon@gmail.com