Rename tracker to "reporter" (or similar)

[benvinegar]

I borrowed this terminology from Fathom (tracker.js is a fork of that project's script), but I don't think it's good name:

1. "tracker" sounds anti-privacy
2. The script doesn't actually track you – I deleted all the cookie-related code from the script

I think reporter.js would be more accurate.

If we did this, we should continue publishing tracker.js for backwards compatibility (e.g. users could upgrade to the latest version of Counterscale and not need to update their script references).

[lrh11099]

Reporter.js sounds too generic. counter.js based on project name sounds nice, but might be limited in scope.

[benvinegar]

Yeah counter.js is a good idea. Fits the name, could even work as a branding element (e.g. people see counter.js in the network tab, more obvious what it is).

Re: limited in scope – that's also fair. But I don't think the name has to limit what it does. For example, there could be a future where it collects basic latency/web vitals, and yeah that's not "counting" but IMO it's still fair game.

Will sit on this for a bit.

[lrh11099]

Yeah counter.js is a good idea. Fits the name, could even work as a branding element (e.g. people see counter.js in the network tab, more obvious what it is).

I agree. I also thought about count.js, insights.js, metrics.js cs.js (CounterScale) etc. But keeping a part of the brand name like counter.js seems better.