31–40 of 129 posts
As a user of the open source version of Fathom, I'm a little concerned by the lag in publishing this update to the community edition. I assumed development work was happening in the open on Github, but I guess that's not the case?
Whole new language & codebase. Old developer left, we don't write Go.
Earlier quoted context omitted.
Thanks for the concern here. We are GDPR compliant (and may be exempt from it). See here: https://usefathom.com/data/
You might like to edit the line on that policy page that refers to "the most privacy-focused manor"... while a privacy-focused manor is an interesting idea, I suspect you meant "manner". :)
sorry but, isn't that a (unnecessarily complex) cookie?
It's so exciting that thanks to GDPR we are now seeing innovate analytics solutions that respect privacy.
Looks decent, but pricing is insanely high for the extremely limited set of stats.
Earlier quoted context omitted.
So it's not as easy as just pushing the update to the repo. We are still committed to open-source, but we also have a business to run and need to make a living here (we're two dudes who care about privacy, not a huge company with deep pockets) :) The community version is getting a full update soon. We just have to focus on profit a bit (this keeps us in business and able to update the repo).
There's certainly nothing wrong with that. But this sounds a little defensive. And if you're going to promote the "Community Edition"/open-source nature of the codebase, this should probably be made more clear to your users/contributors. (Maybe it is made clear and I'm just not seeing it, though - this is my first time hearing about this product).
Couldn’t people just parse the log files from their webservers?
Earlier quoted context omitted.
Thanks for the concern here. We are GDPR compliant (and may be exempt from it). See here: https://usefathom.com/data/
Tell me if I get this correct: Alice visit a site and gets the hash 1234. The analytics data is stored and associated with hash 1234, but soon after, hash 1234 is removed. However the aggregate visitor analytic that was associated with hash 1234 data persists. Then another user (say Alice again) returns and gets hash 5678. Analytic data is tracked, stored with hash 5678 for the 30 minutes (or less), and then hash 567…
Earlier quoted context omitted.
Whole new language & codebase. Old developer left, we don't write Go.
So it's not as easy as just pushing the update to the repo. We are still committed to open-source, but we also have a business to run and need to make a living here (we're two dudes who care about privacy, not a huge company with deep pockets) :) The community version is getting a full update soon. We just have to focus on profit a bit (this keeps us in business and able to update the repo).