DefiLlama

Graz OdonDeveloperJul 8, 2024

Almost everything in this review is wrong, let's go through it point by point: > the extension was repeatedly spawning a worker component which in turn was making network requests to compare ALL OPEN TAB URLs to a list of URLs from the extension github repository... One of the features that this extension has is that the icon changes to red if you're on a scam page. In order to do that we need to check the current URL. We DON'T make a network request every time to compare URLs, instead we just fetch the list on startup and then regularly update it and keep it in cache to keep using it. > While that's probably just to check if visited URLs match those the extension is set to work on... This is NOT how browser extensions work, extensions that just inject code on some pages don't need to do that. Our extension checks URLs because the icon changes to red on scam pages and we need to check URL to provide that feature. > THIS SHOULD ONLY HAPPEN FOR THE CURRENTLY ACTIVE PAGE, AND NOT FOR ANY OTHER BROWSER TABS! ALSO, IF THE EXTENSION IS SET TO ONLY ACTIVATE ON CLICK, THIS SHOULD NOT RUN AT ALL, NOT EVEN FOR THE CURRENTLY OPEN TAB. I don't understand where did you get that this extension is set to only activate on click. This was NEVER the case, we never said this anywhere, when you install the extension the permissions are clearly different from that and the images and text on the listing clearly state that we change etherscan pages automatically so its not on user click. The quote you use in your own review states that the extension injects token prices and wallet tags, so you must clearly be aware that this is what the extension does automatically, and how would it do that automatically if it only activated on click? Please send us a link with any instance where we said this only activates on user click. > UPDATE: THIS BEHAVIOR SEEMS TO BE CONFIRMED BY ANOTHER USER ON GITHUB [1]. FOR ME THIS IS ENOUGH TO IMMEDIATELY UNINSTALL AND REPORT THIS EXTENSION. This is completely unrelated. What happened is that we updated the extension to have access to more pages so we could apply changes to other block explorers and twitter, instead of only the initial explorers. We stated the new permissions on the chrome store listing, announced them our twitter, and the extension was disabled for all of our users until they manually accepted the new permissions. However, we forgot to update our readme on github to say it, which is what that user is saying. That has nothing to do with the extension activating on click or any of the other issues you mention, I don't understand why you bring this up as some kind of evidence when it's clearly unrelated. In conclusion, it seems you came up with the idea that extension activates only on user click, which is contrary to what's on the extension listing, the extension's core functionality, and what the quote you used says, and then got mad at us because the extension doesn't do that.