pirsch

I'm rewriting the open-source core [0] of our product [1] to add more flexible reports. This is the first time I'm building with the help of AI (Claude), but I don't really let it write code. It has been really helpful in discussing ideas (I'm mostly working alone), like a rubber duck that actually talks back. The code it generates however has many subtle and sometimes obvious mistakes in them, so I decided to write the code myself. The main benefits over the previous version will be: - Dynamic reports (ClickHouse queries are generated on the fly) - Better performance - Much cleaner and less code - Better and faster data ingestion including new features, like full support for JSON metadata - And much more It feels kinda crazy that I've been working on this project for more than 5 years now and it's still exciting :) [0] https://github.com

Nice, how is it different from: https://github.com/umami-software/umami https://github.com/arp242/goatcounter https://github.com/swetrix/swetrix https://github.com/pirsch-analytics/pirsch

Pirsch analytics is a great one https://github.com/pirsch-analytics/pirsch

You can take a look at Pirsch Analytics [0], which I am a co-founder of. We take privacy very seriously, that is why the core of Pirsch is open-source [1]. [0] https://pirsch.io/ [1] https://github.com/pirsch-analytics/pirsch

I build a logging library for Go, because I couldn't find one that logs to stdout AND stderr. If you used a logging lib on GCP for example, all log output went into the same pile of junk and it was hard to find "real" errors: https://github.com/emvi/logbuch Then there is "null", also because I couldn't find one that got both, marshalling to JSON and be able to store null values in db: https://github.com/emvi/null And finally, our "flagship" open-source project Pirsch, an embedded library for web analytics: https://github.com/pirsch-analytics/pirsch

Fingerprinting. That's what I do for Pirsch (https://pirsch.io/) and I think they do it in a similar manner. You can check out our source code here: https://github.com/pirsch-analytics/pirsch/blob/master/finge... or take a look at the Plausible repo.

A few months ago, I've started a similar analytics project [0], which I have now turned into a product [1] together with my co-founder. The difference to Panelbear is, that I've started this to be used on my personal website, so it was open-source right from the beginning and without the intention to make money. In fact, you can still use our core library for free (AGPL licensed). When we looked at the other solutions out there, we saw that a lot of them offer a self-hosted version for free. Giving away whole products for free has become a trend I don't anticipate. You can be sure there is an open-source, free as in free beer replacement for almost anything, which makes it really hard to build a sustainable business. While you can generate some traction off of it, you also have to deal with people asking for free support, new features, bu

I've found the same issue. A lot of traffic will get blocked if you use a simple JavaScript integration. The solution is (obviously) to track from the backend and provide a simple dashboard for it. I've started building a library [0] written in Go, which I could integrate into my website and until the end of last year, it became a product (in beta right now) called Pirsch [1]. We offer a JS integration to onboard customers more easily, but one of the main reasons we build it is, that you can use it from your backend through our API [2]. We plan to add more SDKs and plugins (Wordpress, ...) to make the integration easier, but it should be fairly simple already. I would love to hear feedback, as we plan to fully release it soon :) [0] https://github.com/pirsch-analytics/pirsch [1] https://pirsch.io/ [2] https://docs.pirsch.io/get-started/ba

I'm working on an open-core product [0] right now, and an aspect I find missing in the article is that you can generate trust by showing how the internals work. This is especially beneficial if you work in an area like us. Of course, you need to make sure your license is set right and you need to think about where new features go, but it's a valid use-case. [0] https://pirsch.io/ open-source core: https://github.com/pirsch-analytics/pirsch

You can check out the Pirsch Analytics core [0]. I'm the maintainer and can answer all your questions :) It probably contains most features you'll use when programming in Go. Take a look at the tracker.go for a concurrent collector. It also has a lot of parsing, a data model, database, http, public API, ... and UI is not required while learning Go I suppose. [0] https://github.com/pirsch-analytics/pirsch

https://pirsch.io/ $4/month if you pay annually or $6 to pay monthly, but free during beta. We are actively working on it right now, but the core is working well and is open-source: https://github.com/pirsch-analytics/pirsch

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 tested, maintained, just like any other software. So, paying something like $4 is worth it, if you don't want to think about it as much. You have a very good looking UI there. I really love the simplicity. [0] https://github.com/pirsch-analytics/pirsch

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

It'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

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