I used to use matomo but I found goatcounter to be simpler to set up and maintain. I also like the UX more [0].
Matomo: Open-source analytics platform
101–110 of 131 posts
Re: Matomo: Open-source analytics platform
#102Earlier quoted context omitted.
Its pretty disgusting to track people against their consent, even more so to circumvent their protections against tracking. I added your domain to my blocklist: https://github.com/lightswitch05/hosts/commit/bb2cd77c9ec028...
Ad blocking != block tracking. If you don’t want to get tracked, turn on Do Not Track in your browser. Matomo and most other privacy focused analytics scripts respect that setting.
Sure, so I have tracking protection too both through uBlock Origin, and Firefox' tracking protection feature. Yet, here you are, bypassing my tracking protections.
Re: Matomo: Open-source analytics platform
#103Earlier quoted context omitted.
Ad blocking != block tracking. If you don’t want to get tracked, turn on Do Not Track in your browser. Matomo and most other privacy focused analytics scripts respect that setting.
Sure, so I have tracking protection too both through uBlock Origin, and Firefox' tracking protection feature. Yet, here you are, bypassing my tracking protections.
If you're using Firefox tracking protection (which I'm guessing using DNT as well), then Matomo by default does not track you though. So no, your tracking protections aren't being bypassed.
Re: Matomo: Open-source analytics platform
#104Earlier quoted context omitted.
Its pretty disgusting to track people against their consent, even more so to circumvent their protections against tracking. I added your domain to my blocklist: https://github.com/lightswitch05/hosts/commit/bb2cd77c9ec028...
It's your call really, but a website owner tracking you with their own software on their own Matomo instance is not the problem. This is essentially the same as monitoring website logs... that's not disgusting at all.
I think grouping server-side tracking with JavaScript based tracking is an oversimplification. JavaScript tracking is much more invasive and can access significantly more data. From something as straightforward as fingerprinting to potentially even more invasive data such as geo-location, battery status, webcam, microphone - you name it. Server access logs aren't going to track my eyes.
I think we can all agree there are different levels of acceptable tracking and use of that data- but the degrees of acceptance are going to be different depending on the user and service. I don't consider bypassing my restrictions to run unauthorized code to be an acceptable tracking method and raises serious concerns about how the data will then be used.
Re: Matomo: Open-source analytics platform
#105I just wished it used Clickhouse as persistence layer.
Re: Matomo: Open-source analytics platform
#106Is 1.7k open issues something to worry about or is it normal for a project of this size? PS: I have also been building something similar, but not completely open-source: https://www.usertrack.net
While I agree that 1.7k issues are a lot, also keep in mind that there are 9.6k closed issues and they are bugs and feature requests over 11 years that never get closed as there might be someone else coming across some feature request one day who wants to implement it.
Fun fact that should be point out: Most of those issues and pr’s comes from core team members. There is almost no community around it, but looking at these numbers you get the impression that it is otherwise.
Re: Matomo: Open-source analytics platform
#107I have setup a load balancer with 3 instances of matomo connected to one mysql database to handle tracking on a website with around 7000 visits a day. It could all probably be handled by just one instance but that is sort of the standard setup we have for things.
matomo is very comparable to google analytics in terms of reports. matomo has some things that seem a little easier to get to; like visitor flows.
However, matomo seems to just give up on big data, complex reports. Similar reports in google analytics take a long time to complete, 10 to 40 seconds, but they at least complete; eventually.
Re: Matomo: Open-source analytics platform
#108Re: Matomo: Open-source analytics platform
#109Earlier quoted context omitted.
It's your call really, but a website owner tracking you with their own software on their own Matomo instance is not the problem. This is essentially the same as monitoring website logs... that's not disgusting at all.
I think grouping server-side tracking with JavaScript based tracking is an oversimplification. JavaScript tracking is much more invasive and can access significantly more data. From something as straightforward as fingerprinting to potentially even more invasive data such as geo-location, battery status, webcam, microphone - you name it. Server access logs aren't going to track my eyes. I think we can all agree there…
OTOH JavaScript tracking is an easy way to filter out a lot of the bots. I use a little bit of JS-based tracking for exactly this reason, but I'm not extracting anything that wouldn't show up in server logs (eventually I also want to get some "time spent on page" metric so I have some idea how useful my blog posts are (are people clicking and leaving right away or are they sticking around to read). You pretty need JS for this. In whatever case, web analytics like these aren't "tracking"; you're looking at user behavior on your own site; not trying to follow them around the Internet or otherwise identify them.
Re: Matomo: Open-source analytics platform
#110Earlier quoted context omitted.
It's your call really, but a website owner tracking you with their own software on their own Matomo instance is not the problem. This is essentially the same as monitoring website logs... that's not disgusting at all.
I think grouping server-side tracking with JavaScript based tracking is an oversimplification. JavaScript tracking is much more invasive and can access significantly more data. From something as straightforward as fingerprinting to potentially even more invasive data such as geo-location, battery status, webcam, microphone - you name it. Server access logs aren't going to track my eyes. I think we can all agree there…
Anyone can do all sorts of things. I can punch anyone I see on the street in the face. Doesn't mean they're actually doing it.
Now, I have a vested interest in this as I work on one of those tracking tools, but it actually collects less data than those Apache access_logs that people have been keeping for 25 years. Plus, the JS is unminified and easily examinable if you want (as is the HTTP request), so you also have more insight in what is being collected exactly.
"It's using JavaScript" and "it can do [..]" are massive red herrings; browsers are actually fairly sandboxed and there are millions upon millions of lines of code on your computer that can do much more than JavaScript inside a webpage.