As a user, I dont see tracking by specifically google being the problem; what I'm against is being tracked _at all_ - by anyone, self hosted or not.
There's "caring about privacy" in the subheadings, yet there's a whole section in docs about collecting private data [1]. Empty words.
I've used goaccess [2] in the past to provide traffic analytics. It reads from nginx/apache logs. You only get access to what browsers send anyway, and users who alter their user agents are in the minority, so they wont affect analytics much.
As a user, I dont see tracking by specifically google being the problem; what I'm against is being tracked _at all_ - by anyone, self hosted or not.
There's "caring about privacy" in the subheadings, yet there's a whole section in docs about collecting private data [1]. Empty words.
I've used goaccess [2] in the past to provide traffic analytics. It reads from nginx/apache logs. You only get access to what browsers send anyway, and users who alter their user agents are in the minority, so they wont affect analytics much.
[1] https://github.com/electerious/Ackee/blob/1cf7779/docs/Anony...
[2] https://goaccess.io/