ad blockers block my tracker.
not the creepy one. mine. the one that stores no cookies and no ips.
i'm om yaduvanshi, 18, an applied ai developer. i build cloudline, a cookieless analytics tool. day 29 of 90, building in public. it launches tomorrow.
the page that lists my enemies
every tracker needs a troubleshooting page. mine lists four ways it can fail: your content security policy can refuse the script, an ad blocker can eat the request, localhost events get refused in production, and the domain can just not match.
i wrote all four down instead of pretending they don't happen. a visitor with a blocker shows up as a visitor who never loaded the script. i won't know they visited. that's the price.
why i don't fight back
the fix exists. i could rotate domains, disguise the request, do the cat-and-mouse thing the creepy tools do every day.
every trick that would beat a blocker is a trick i refuse to use. so the script stays dumb. one tag, under 2kb, from one domain. if your blocker takes it down, it takes it down.
the honest part of the dashboard
what i can do is be honest about what's missing. when cloudline can't collect something, the dashboard shows an error message instead of a made-up number. no silent zeros pretending to be real data.
same instinct as the demo badge and the labelled roadmap. if the number isn't there, you should see that it isn't there.
one day left
launch day is tomorrow. day 30 of 90. the thing i'm most sure about after 29 days: people don't punish you for the missing parts. they punish you for the hidden ones.
day 29 of 90. see you tomorrow.
cloudline is free while in early access. no card.
— om
Top comments (0)