111–120 of 139 posts
Earlier quoted context omitted.
> Analytics in general does nothing to help the users of your site while pushing additional work onto the client and leaking information. Analytics are a very useful tool to use in order to improve a product.
If that formula could be perfected it could be automated without gathering data that can be used for other purposes?
I applaud anyone one makes an effort to avoid thirdparty analytics products. Analytics in general does nothing to help the users of your site while pushing additional work onto the client and leaking information. But looking at data is fun so I ended up creating my own super light counter that I run on my site so I can see hits. My goal was to store as little information as possible - only hit counts as stored, and n…
Maybe you should look at the analytics and determine your traffic sources. What pages are the most popular and in what markets?
But of course, there goes that dirty word "analytics" which "does nothing to help the users of your site"...
First time I've ever seen a comment about accessibility on the homepage of a mainstream product like this. As a blind developer this was just awesome, made me really feel like somebody out there is listening. Thank you for making this
Does anyone know of a good resource for this?
One tool I'd suggest looking into when getting started is Accessibility Insights for Web. A team at Microsoft developed a free, OSS browser extension for automatically detecting most common accessibility issues on your site: https://accessibilityinsights.io/docs/web/overview
Disclaimer: I do work at Microsoft, but my only affiliation with Accessibility Insights is as a happy customer :)
First time I've ever seen a comment about accessibility on the homepage of a mainstream product like this. As a blind developer this was just awesome, made me really feel like somebody out there is listening. Thank you for making this
Does anyone know of a good resource for this?
Can someone explain the attraction of embedded JS for analytics, what exactly does it buy you versus log parsing? Log parsing seems like the logical choice for the static site crowd but it seems like there's little interest there. I must be missing something.
Out of curiosity, what are the options for log parsing? The ones I know are Awstats and Webalizer. Is there any more up to date or more modern alternative to these two?
Can it also run in "server log parsing" mode so that no JS scripts are required? This makes it even easier to avoid processing personally identifiable information (if you don't collect the full IP) and it works even if people have JS disabled (or if the clients are automated scripts). Matomo is quite good at this.
No, but this wouldn't be too hard to add. I'm not planning to work on it soon, but I'll be happy to review PRs/provide guidance on how to build it. I will add docs on how to run it in "server mode", where instead of using a JS script you add a HTTP request in your apps middleware. This is an idea I had the other day and I did some research on it, and it should work quite well (haven't started work on it yet though).
Regarding log analysis, it can be tricky to get right due to logrotate edge cases.
Earlier quoted context omitted.
The most obvious one I miss (I don't currently only use server-side analytics) is something like screen size. You can do user-agent sniffing to _guess_ what the size of a mobile device is, but it doesn't tell you whether or not you can stop wasting time making your content responsive on a tiny screen that no-one uses anymore.
You can do this with only media queries in CSS, most likely.
First time I've ever seen a comment about accessibility on the homepage of a mainstream product like this. As a blind developer this was just awesome, made me really feel like somebody out there is listening. Thank you for making this
Does anyone know of a good resource for this?
Can someone explain the attraction of embedded JS for analytics, what exactly does it buy you versus log parsing? Log parsing seems like the logical choice for the static site crowd but it seems like there's little interest there. I must be missing something.
others have pointed out:
- Client side SPAs sometimes don't hit server logs
- Some static sites are hosted places where you don't have access (github pages, netlify, etc)
- Bots are sometimes defeated by a simple js file
But another one that is not mentioned is one that effects large apps and services. Many large apps and services don't exist on a single server. Furthermore servers are launched and destroyed on a whim to meet scalability needs. Javascript analytics easily surmount this. I suppose it is still possible to feed multiple server logs into a single source of truth for analytics, but I dont know if such a solution exists right now. JS Analytics easily overcome this obstacle.
Can someone explain the attraction of embedded JS for analytics, what exactly does it buy you versus log parsing? Log parsing seems like the logical choice for the static site crowd but it seems like there's little interest there. I must be missing something.
A few reasons have been pointed out by others, but let me include another. others have pointed out: - Client side SPAs sometimes don't hit server logs - Some static sites are hosted places where you don't have access (github pages, netlify, etc) - Bots are sometimes defeated by a simple js file But another one that is not mentioned is one that effects large apps and services. Many large apps and services don't exist…