4 ms·
Off the top of my head, based off things we normally look for in our analytics: - See how people get to the privacy page from where they enter the site. Useful
by Osmose 11y ago
Off the top of my head, based off things we normally look for in our analytics:
- See how people get to the privacy page from where they enter the site. Useful to see if some categories are getting more traffic than others, so that we can re-balance if, for example, we think that Privacy is not getting the attention we want it to.
- See how long people are staying on this page. What if the writing or infographic don't make sense to users? We can try and improve them so that users come away with a better understanding of privacy.
- How are users interacting with those circles? If they're not hovering over any of the circles, maybe we should make it auto-switch between them to draw the user's eye over. Or maybe if they're only hovering over the first three, we should make those first three the most important aspects of privacy to make sure they're seen.
The goal of Shape of the Web is (in my eyes) to educate users about the issues that the open internet faces today, and to help give them a framework for thinking about what the web is (it's hard to think about a thing if you don't know how it's "shaped"). All of these metrics help us improve the page's ability to convey information so we can better educate users.
- pdkl95 11y ago> - See how people get to the privacy page from where they enter the site. You don't need a 3rd party to learn the order of pages you served to any given client. That one is so simple you only need 'grep' and the server log. (aggregation into whatever statistics you want to learn is a trivial exercise left for the reader) > - See how long people are staying on this page. The entire point is that you do not have a right to that information, other than what you can infer from the client later loading another page. Applying technical methods to gain access to private information like this simply makes you the the spy invading people's privacy. Worse, as most people do not understand these technical details, you are a eavesdropper who is preying on ignorance. > so that users come away with a better understanding of privacy. ...while you simultaneously violate the same user's privacy. Do you seriously not understand that you're making the "We had to destroy the village in order to save it" style of ends-justify-the means argument that ignores how you've started to act like that which you are supposedly fighting against. > hovering over Again, the entire point is that you don't get to know that information. That is a perfect example of the type of data the privacy-focused people are trying to protect. We really don't give a damn if that information is useful; if you're recording anything beyond the HTTP requests you receive (the explicit request from the client), then you are the spy and therefore the enemy. If you want to understand how effective your pages are, find another way to deduce that information. This is why traditional businesses pay people to participate in focus groups, to name one example.