4 ms·
To anyone that has ever tried to parse their http server's access logs, this is something that they realize and come to the same conclusion. This is one of the
by dylan604 2y ago
To anyone that has ever tried to parse their http server's access logs, this is something that they realize and come to the same conclusion. This is one of the reasons why third party statistics like GA exist. If this was a blog from someone that this was their very first attempt ever at parsing logs, this might seem more reasonable. However, this person claims they know parsing access logs is frustrating and yet claim this was a novel/clever idea which does not compute.
Just a simple web search on issues parsing access logs would show this is not a new idea nor would it be a successful one.
- tootie 2y agoThis is a big issue with podcast analytics since most downloads come via podcast apps that don't allow any client code at all. We only have server logs to go off of and hence problems like NAT are essentially unsolvable.
- throw1902378190 2y ago> One of my recent clever ideas was to look for IP addresses that requested content here using several different HTTP 'User-Agent' values I'm always surprised when a blog post like this makes it to the front page of HN. I suspect that their only experience with web hosting is this blog as there's nothing clever or interesting about their experiment.
- dylan604 2y agoI always chalk it up to those that refuse to look at history are doomed to repeat it.