Coding in the open: how to do it securely

Re:Coding in the open: how to do it securely by icebraining on Wednesday September 27, 2017 @11:40AM (#15348897)

Nope, just not taken far enough: don't run analytics at all.

[ Parent | on HN ]

Re:Coding in the open: how to do it securely by robin_reala on Wednesday September 27, 2017 @11:58AM (#15349095)

Then you fail design principle three: Design with Data. https://www.gov.uk/design-principles#third

[ Parent | on HN ]

Re:Coding in the open: how to do it securely by Nursie on Wednesday September 27, 2017 @12:29PM (#15349436)

Failing a design principle is surely less important than security of citizen/government interactions?

[ Parent | on HN ]

Re:Coding in the open: how to do it securely by mathieuh on Wednesday September 27, 2017 @01:33PM (#15350187)

I 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.

[ Parent | on HN ]

Re:Coding in the open: how to do it securely by Nursie on Wednesday September 27, 2017 @02:45PM (#15350980)

Then why is GA still there at all?

[ Parent | on HN ]