Also a very interesting approach. The difference to counter.dev is that counter.dev does not need any hashes or any unique ids at all, which saves complexity and avoids needing to explain why our specific way of using hashes or ids is privacy friendly. As we have none.
Comments
This is not directly related to Counter, but here is a nice explanation of how GoatCounter[1] has implemented session tracking: https://github.com/arp242/goatcounter/blob/master/docs/sessi...
[1]: https://www.goatcounter.com
Also a very interesting approach. The difference to counter.dev is that counter.dev does not need any hashes or any unique ids at all, which saves complexity and avoids needing to explain why our specific way of using hashes or ids is privacy friendly. As we have none.