Why Better Likes asks for an email
Reading reactions on Better Likes is fully anonymous — no sign-in required. But
to leave one of your own, we ask you to verify a working email address once.
This page is about why, in everyday terms.
The short version
A reaction count is only worth looking at if "one user" really means "one
person". Better Likes could have skipped sign-in entirely, or asked you to log
in with Google or GitHub. Both shortcuts looked simpler on paper, and both
quietly break the number on the screen. One-time email verification was the only
option that keeps the count honest and respects your privacy.
Option 1: just use your device as your ID
Why it sounds great
No sign-in. No email. No friction. The extension installs and instantly knows
who you are. Many similar extensions take this route — they generate a random
number when you install, or they fingerprint your device (the operating
system, the screen size, the timezone, that sort of thing), and use that as
your identity.
Sounds perfect. It isn't.
Why it falls apart in real life
A device or a browser is not the same thing as a person. Here are everyday
situations where the "device = person" idea breaks, and what it means for the
counts you see:
- You reinstall your browser. To the extension you are now a brand-new
person. The reactions you left this morning are from "someone else" now. Or: someone trying to inflate a number just reinstalls.
- You use Chrome at work and Firefox at home.
That's two different people, as far as the extension is concerned. Your reaction
counts twice.
- You buy a new laptop. Old you is gone, new you appears.
- Your operating system updates and changes something tiny. Sometimes
that's enough to "look like" a different device. New person.
- Two people own the exact same laptop model. They can end up looking
identical to a fingerprinting system, even though they're different people.
The system merges them. One real vote shows up as two — or two people share a
single vote.
The end result is the same in every direction: the counts drift. They're
either inflated by the same person being counted as several, or deflated by
several people being counted as one. And anyone who wants to push a number
around can just open a new browser profile — which is free, instant, and
infinite.
Option 2: sign in with Google or GitHub
Why it sounds great
Most apps these days have a "Continue with Google" button. It's familiar, it's
one click, and it solves the "one person, one account" problem because Google
already knows who you are. It would have been easy to bolt on.
Why we decided against it
Three reasons, and any one of them on its own would have been enough.
- Privacy. A "Continue with Google" button tells Google that you
use Better Likes. We don't think a tiny reactions extension has any business adding
a row to your Google profile. Same for GitHub and Microsoft. You came to Better
Likes to leave an emoji on a Facebook post, not to broadcast that fact to a third
party.
- Lock-in. If Google or GitHub decided, tomorrow, to disable Better
Likes's sign-in app — by mistake, by policy change, by automated false positive
— every single user would be locked out at once. Trusting our whole identity layer
to a giant we don't control is a risk we don't want to take with your account.
- The "two accounts" problem. Lots of people have a work Google
account and a personal one. With OAuth you can sign in with either, and the extension
thinks you're two different people. That's the same problem as the device-ID approach,
just dressed up nicer.
Option 3: a one-time email code (what we picked)
What you actually do
The first time you want to leave a reaction, Better Likes asks for your email.
We send a 6-digit code. You paste it in. You don't have to do this again for a
month. That's the entire flow.
Why this is the only honest option
- It's still you on every browser. Sign in with the same email
in Chrome at work, Firefox at home, on your phone — same account, same history,
same one vote per post.
- Reinstalling doesn't reset you. Your email didn't change, so
neither did your account.
- It costs real effort to be fake. Making a hundred working email
addresses is much harder than opening a hundred browser profiles. That's the friction
that keeps a count meaningful.
- No third party gets to know. You don't tell Google, GitHub, or
Microsoft that you use Better Likes. The only thing that learns your email is
your own email provider — which already knows.
- Anyone with email can use Better Likes. You don't need a Google
account. You don't need GitHub. You don't need an account anywhere else. You bring
your own email, even on a custom domain, even from a tiny provider.
What happens to your email afterwards
We send the code over a secure connection, your email provider delivers it to
you, you paste the code back, and then we forget the email itself. We don't
save it. We don't sell it. We don't email you a newsletter — there isn't one.
The only thing we remember is a one-way scramble of the email that lets us
recognize "this is the same person" the next time you sign in. Even if someone
broke into our database tomorrow, they could not recover your email address
from what's stored.
And if you change your mind, the popup has a "Delete account" button. One
click and the record is gone, and the reactions you left over time are
subtracted back out of the counts they belong to. No support emails, no "are
you sure", no waiting.
The three options, side by side
| Device / fingerprint | Google / GitHub sign-in | One-time email (us) |
| Same you across browsers? | No | Yes | Yes |
| Survives a reinstall? | No | Yes | Yes |
| Third party learns you use Better Likes? | No | Yes | No |
| Can a giant tech company lock everyone out? | No | Yes | No |
| Hard to fake at scale? | No — free reinstalls | Sort of — but multi-account confusion | Yes — every fake account needs a working inbox |
| Friction the first time | None | One consent screen | Paste a 6-digit code, once a month |
| Counts can be trusted | No | Mostly — except multi-account users | Yes |
The short answer to "why email?"
Because the alternatives quietly break the number on the screen, and we didn't
want to ship a number we couldn't stand behind. A device ID is not a person. A
Google login is a person plus a leak. A one-time email code is a person,
and only a person, with nothing leaking out the back.
And because we'd rather earn one small click from you every month than ship a
number that's wrong in your favor.