MAmarvinblum·Dec 17, 2020
Probably like we do it for pirsch.io, by calculating a hashed fingerprint and throwing away the individual page hits once per day: https://github.com/pirsch-analytics/pirsch
In No Cookie for Youpirsch-analytics
pirsch
Go2020–2026
pirsch-analytics / pirsch
pirsch
Pirsch is a drop-in, server-side, no-cookie, and privacy-focused analytics solution for Go.
4Distinct people
20Mentions
1Explicit recommenders
1KGitHub stars
What to know before exploring
What it is
Pirsch is a drop-in, server-side, no-cookie, and privacy-focused analytics solution for Go.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
I did the same for my Go library [0], but I don't think it's "pretty easy" if you want to do it right. Especially filtering out bots is a constant hassle, it needs to be…
marvinblum used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 3:38:16 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year20 dated mentions
Observed mentions: 2020-06-28 12:27:39 UTC to 2026-06-15 10:59:13 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 9 | 0 | 9 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
8 sourcesIt's important to set boundaries early on. I'm working on this analytics library [0] and this game server management app [1] at the moment.
I started the first one with my own website in mind and as it gained some popularity, decided to try to make a commercial product out of it. Instead of making everything open-source, I develop the platform closed-source and keep the core (this library) open-source, but set limits to what can be contributed and under what conditions. This isn't clearly communicated in the repo yet, but it helps to stay sane.
For the game server project, which is older, I see a lot of feature requests and small contributions, because people actually depend on it. But boy, the support requests drive my crazy sometimes. Even if you only have a hand full of users, they can get demanding some days, when a new DLC for the ga
Read the rest
me is released for example. I really want to support it and keep it up-to-date, but I sometimes have to ignore them. This week someone asked me if I could support them setting it up as they had trouble making it work for their drivers. Turns out they're a professional e-sports team. As soon as I asked for compensation, they didn't write back (after sending them 4-5 emails, taking half an hour to write). This is when it gets frustrating...
I don't know how to fix the issue, but we, as open-source maintainers, should value our time.
[0] https://github.com/pirsch-analytics/pirsch
[1] https://github.com/assetto-corsa-web/accweb
I'm working on an open-source analytics lib [0] and I fully agree with the article that Cloudflare should either do it right, or not do it at all. Filtering bots is probably the hardest part and time consuming. There is no simple approach to solve the issue, but not doing it at all makes it worthless, especially for the price.
Hopefully their push will make the issue more prominent to website owners and help Google Analytics alternatives to grow.
[0] https://github.com/pirsch-analytics/pirsch
In Cloudflare Analytics reviewHello Hackers, we're working on a new product. A developer friendly analytics tool that respects the privacy of your website visitors. We will offer SDKs, an API, good documentation and more. The core is open-source and available on GitHub: https://github.com/pirsch-analytics/pirsch (we will probably change the license).
Please sign up for our upcoming beta if you're interested. We plan to launch the beta at the end of this year and it will be completely free.
In Show HN: Pirsch Analytics – upcoming privacy and developer friendly analyticsFingerprinting. I'm working on a competing product which is also open-source. This is how I do it: https://github.com/emvi/pirsch/blob/master/fingerprint.go
And I think that is what most privacy-focused solutions do at the moment.
In Show HN: Plausible – Self-Hosted Google Analytics alternativeShow HN: Pirsch – Server-Side Tracking Without Cookies in Go
3 points · Open discussionYou can compensate for it a bit by reading the X-Forwarded-For header. In case someone sits behind a proxy, they usually set this header with the actual IP address of the client. You can see this here: https://github.com/emvi/pirsch/blob/master/fingerprint.go#L2...
In Show HN: Server-Side Tracking Without Cookies in GoI'm already seeing a lot of of bot traffic via HN and started a list here: https://github.com/emvi/pirsch/issues/1 Feel free to add more!
In Show HN: Server-Side Tracking Without Cookies in Go