Ben Vinegar

I think because comparable products strip the query string, and because Counterscale promotes itself as being privacy-sensitive, it's worth doing the same (removed in c6493a5).

Hey @eurica, thanks for the feedback 🙏 (Sorry, read this via email but forgot to respond here!)

Thanks again @eurica for the comments. The installation process changed dramatically in [v3.0.0](https://github.com/benvinegar/counterscale/releases/tag/v3.0.0-rc.0) – now there's a step-by-step CLI wizard that simplifies much of this (e.g. explains inline what permissions...

First off, thank you for picking up an issue and contributing. 🙏 > Does it cover your usecase @benvinegar? Some thoughts that come to mind: * It should probably account...

> Is there any reason to not just do something like this? You totally could – but the reason to use `data-` attributes is so that users who have [disallowed...

Fixed via #132

That's exciting – just a note about this disclaimer in the README: > NOTE: Counterscale is currently in very early development and shouldn't be used in any actual production setting....

> Let's see how it reacts but the initial impression is that the dashboard opening is slow. I'm feeling that too on counterscale.dev. It basically queues up like 8 simultaneous...

Perf issues documented in #68 Playing around, I don't feel `956163c` is the cause. Even queries with low intervals (e.g. 7 days) can randomly just take 10 seconds.

Oh interesting. I mean, this behavior was forked from Plausible's script (the license and copyright is maintained at the top of the file). I didn't think too much about why...