Is Yeah! for Twitter safe?
Yeah! for Twitter sends visible tweet IDs to its API while you browse Twitter/X.
When you view Twitter/X pages, the extension scans visible tweets, extracts their status IDs, and queues them for Yeah-count lookups. If you are authenticated with Yeah!, it batches up to 100 uncached tweet IDs at a time and sends them with your stored Yeah token to its API.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itdimden.dev - 1 other listing from the same operator, none carrying a finding
dimden.dev - 1 other listing from the same operator, none carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
1 other listing published from this account, 80k+ users between them, none of them carrying a finding.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 1.1.4. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on twitter.com
*://*.twitter.com/* and 1 more
Read and change your data on twimg.com
*://twimg.com/* and 1 more
Read and change your data on x.com
*://x.com/* and 1 more
Read and change your data on dimden.dev
*://*.dimden.dev/*
Store data in your browser
storage
Where it sends data
Destinations our analysis observed Yeah! for Twitter contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- yeah.dimden.dev
Yeah! for Twitter sends data to yeah.dimden.dev. No other extension we have analysed sends data here.