# RFC: Proposal for estimating unique Julia clients without tracking

**URL:** <https://discourse.julialang.org/t/rfc-proposal-for-estimating-unique-julia-clients-without-tracking/138027>\
**Category:** General Usage\
**Tags:** statistics, pkg, cryptography, rfc\
**Created:** [July 9, 2026, 9:07am UTC](https://discourse.julialang.org/t/rfc-proposal-for-estimating-unique-julia-clients-without-tracking/138027 "2026-07-09T09:07:34Z")\
**Posts on this page:** 1\
**Showing post:** 67

<div class="post-metadata">

**Author:** ![Mason](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mason/32/2423_2.png) [@Mason](https://discourse.julialang.org/u/Mason)\
**Post date:** [August 10, 2026, 10:41am UTC](https://discourse.julialang.org/t/rfc-proposal-for-estimating-unique-julia-clients-without-tracking/138027/67 "2026-08-10T10:41:08Z")

</div>

> [@foobar\_lv2](#):
>
> You’re thinking too small.
> 
> If I want reader statistics for my blog, then your proposal is a good way to do this. There is a not insignificant population who (A) wants statistics on resource-using clients, aka readers, and (B) hates cookie-banners, and (C) cares about their user’s privacy, and (D) also cares about the general politics of user privacy.
> 
> That would require a small javascript implementation of the client-side protocol, putting the key-material (i.e. the user’s statistical-tracking-identity) into localStorage.
> 
> In a perfect world, the necessary machinery would be part of web-browsers, such that users don’t need to trust the javascript library (this won’t ever happen).

Wow, I didn’t think of this. That could actually be quite impactful.

---

_[View the full topic](https://discourse.julialang.org/t/rfc-proposal-for-estimating-unique-julia-clients-without-tracking/138027)._
