4 ms·
Sure, it’s possible to run your own analytics achitecture but at a 100m visits a month is it practical? Point two of the GOV.UK design principles is to do less:
by robin_reala 9y ago
Sure, it’s possible to run your own analytics achitecture but at a 100m visits a month is it practical? Point two of the GOV.UK design principles is to do less: https://www.gov.uk/design-principles#second https://www.gov.uk/design-principles#second . When GOV.UK first started it definitely had to hit the ground running which requires immediate evaluation of user data ASAP. Certainly at the time there wasn’t enough dev hours available given a limited number of people to evaluate, build and run an analytics framework of the scale necessary.
Having said that, then isn‘t now, and I wouldn’t be surprised if a future Government as a Platform service isn’t a cross-government analytics system hosted from the UK. I just don’t see the pressing need for it, based on the assumption that Google actually are anonymising the data. If you want to disagree with that assumption then that’s a valid viewpoint too, but I see no evidence for it.
- vog 9y ago> based on the assumption that Google actually are anonymising the data. If you want to disagree with that assumption then that’s a valid viewpoint too, but I see no evidence for it. This is exactly the wrong way around. For every sensitive area, such as privacy, it is upon the company to prove proper handling of data. But if that company is outside your legislation, without any legal means in their country, how could that ever be possible? Taking just their word is like trusting the food industry with hygienics until their customers become undeniably sick. A better strategy is not to create sensitive datasets in the first place. In Germany, this principle is called "Datensparsamkeit", which could be translated to "data frugality". Moreover, every country should have something like the FDA for data hygienics. Unfortunately, even in Germany where we do have "Datenschutzbeauftragte" (designees for data protection), those can make a lot of noise but don't have much power. This is still better than not having those people, though.
- robin_reala 9y agoI’m not disagreeing with you outright, but your argument is on the ad infinitum scale. For instance, GOV.UK PaaS uses AWS as a host[1]. Is that worrying? Should we not be using Cisco gear because of US govt backdoors? Should we not be using Chinese manufactured chips? These considerations are ones the military has daily, but they hinder the ability to deliver. Analytics is arguable both ways (and I lean towards your argument at this point in time) but there are good reasons past and present for GA. [1] https://www.cloud.service.gov.uk https://www.cloud.service.gov.uk
- Symbiote 9y agoThose are all maybes. Google Analytics is a certainty, and reasonable alternatives are available. I think it shows a terrible attitude from the department responsible to use GA. Not everything should be done by the lowest bidder, regardless of the costs. Maybe I'll write to my MP...
- Nursie 9y agoThese aren't really equivalent to actively sending out data to overseas entities by anyone using your pages. You absolutely should be taking precautions to make sure that what you're doing on AWS is secure. And in fact erring on the side of using providers who host in European countries, preferably European organisations. (addendum - I spent a lot of the early part of this year working on AWS-based data processing systems for a large bank, they took massive precautions with the transport and storage of their data within the AWS system, including IPSec overlays, 14 day maximum node lifetimes and various other things. I realise that at some point you're trusting amazon, but there's a lot can be done to avoid having problems in the first place. "Not sending data to places you don't absolutely have to" seems pretty basic)
- konschubert 9y ago> Point two of the GOV.UK design principles is to do less: Maybe this particular case is an example where the principle of a lean government fails?
- icebraining 9y agoNope, just not taken far enough: don't run analytics at all.
- robin_reala 9y agoThen you fail design principle three: Design with Data. https://www.gov.uk/design-principles#third https://www.gov.uk/design-principles#third
- Nursie 9y agoFailing a design principle is surely less important than security of citizen/government interactions?
- mathieuh 9y agoI have worked and continue to work on several Gov.UK projects and we take steps to ensure that anything that gets sent to GA is as anonymised as possible. Just last week we had a ticket in planning to further improve the anonymity of the data sent to GA for the UK MOT testing service, so it is definitely not like we’re just firing all sorts of data to third parties, we are thinking very hard about this stuff. Preserving our users’ anonymity is one of our major priorities and we actively work to improve how we do this.
- Nursie 9y agoThen why is GA still there at all?
- IanCal 9y agoIt's also possible to not run analytics on your site if you don't want to spend the effort running something secure within your own country.
- Nursie 9y ago>> Sure, it’s possible to run your own analytics achitecture but at a 100m visits a month is it practical? That's surely secondary to privacy and security? >> If you want to disagree with that assumption then that’s a valid viewpoint too, but I see no evidence for it. I see a whole litany of problems with your assumption, based on the state of the world in terms of large-scale leaks and hacks, on the laws in the US which are much weaker than our own protections, and on the actions of various US agencies when they desire access to privately held information. I see no reason to believe that anonymisation of the date somewhere within google infrastructure is an adequate protection, whether it actually happens as contracted or not. Look, it's clear that you don't consider this important enough to do something about. Some of us do, and some of us would rather that if you can't do this with private analytics, you don't do it at all. And if that makes delivering your service harder, slower and more expensive - so be it. What's happening here is not right. I mean, what you're saying when you reference point 2 of your design principles, is that it's alright to throw user privacy under a bus, so long as you can deliver the software effectively. This isn't a good justification.
- robin_reala 9y agoI don’t actually work for GDS anymore (or even live in the UK) but people there are receptive. Can you leave a comment against the blog post? Unfortunately I don’t know the best way to raise your concerns officially, but that would hopefully get an answer. Actually thinking about it, the best way would be to apply for GDS’s recently opened Deputy Director of Technology and Operations role :) https://www.civilservicejobs.service.gov.uk/csr/jobs.cgi?jcode=1557534&csource=mbs https://www.civilservicejobs.service.gov.uk/csr/jobs.cgi?jco...
- KGIII 9y agoDumb question; is it really all that important that they analyze traffic on a .gov address? If so, for what purpose(s)?
- Kalium 9y ago.gov organizations, like your boring standard-issue commercial ones, also want to know who is using their site and how. It helps inform decision-making about changes.
- KGIII 9y agoThank you. If you don't mind another dumb question, is the benefit great enough for the hassle of complaints and the possible compromise of ostensibly private information? There are self-hosted solutions, but I imagine they'd entail experts to interpret and implement. I wonder if they could just do A/B testing and get the same results or if they could simply do surveys? Though, I suppose those come with new faults, variables, and expenses. Again, thanks for the answer.
- Kalium 9y agoGenerally,yes. It's also good for stuff like knowing what browsers are used and thus what technologies can be used. The hassle of complaints and the possible compromise of "private" information (like what your browser sends) isn't that significant. The pain from complaints is trivial, largely confined to Hacker News threads of no significance whatsoever. The ostensibly private data is protected contractually and legally. I'm not aware of any approach that both yields useful information and eliminates any possible risk of compromise. Surveys and A/B testing and self-hosted solutions all have the same problems and risks, and generally extra costs to boot. In short, the cost-benefit analysis isn't all that different from that of a company considering an analytics tool.
- KGIII 9y agoAgain, much thanks. No more questions, for now. Just a sincere thanks. I don't actually read HN for the articles. I do read many of them, but I'm here for the informative answers, insightful responses, and chances to get an education in subjects I'd not normally consider. Once in a while, chaos theory or traffic modeling come up. So, I get to give back. ;-) Again, my sincere thanks.
- switch007 9y ago> Point two of the GOV.UK design principles is to do less: https://www.gov.uk/design-principles#second https://www.gov.uk/design-principles#second . Or, in full: "Government should only do what only government can do. If we’ve found a way of doing something that works, we should make it reusable and shareable instead of reinventing the wheel every time. This means building platforms and registers others can build upon, providing resources (like APIs) that others can use, and linking to the work of others. We should concentrate on the irreducible core." Slightly different than the title. Can't do privacy because the principle says "Do Less"? Why do anything?