-
Notifications
You must be signed in to change notification settings - Fork 4
/
about.html
94 lines (75 loc) · 6.02 KB
/
about.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
<!DOCTYPE html>
<html class="no-js" itemscope itemtype="http://schema.org/Article">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="css/bootstrap.min.css">
<link rel="stylesheet" href="css/bootstrap-theme.min.css">
<link rel="stylesheet" href="css/c3.css">
<link rel="stylesheet" href="css/main.css">
</head>
<body>
<!-- FIXED NAVBAR -->
<nav class="navbar navbar-default navbar-fixed-top" role="navigation">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target=".navbar-collapse" aria-expanded="false" aria-controls="navbar">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
</div>
<div id="navbar" class="navbar-collapse collapse">
<ul class="nav navbar-nav">
<li><a href="index.html">Data</a></li>
<li><a href="media.html">Media</a>
<li class="active"><a href="about.html">About</a>
</ul>
</div>
</div>
</nav>
<div class="jumbotron">
<div class="page-header" style="text-align: center;margin-top: -40px;">
<h1>Contact / Imprint</h1>
</div>
<div class="container" align="center">
<table width="60%">
<tr align="center">
<td colspan="2" style="padding-bottom: 60px;">For inquiries about data and content please contact<br>Sylvia at <a href="mailto:[email protected]">[email protected]</a>.
</tr>
<tr valign="top">
<td align="center"><img src="img/sylvia.png"/><br/><br/><strong>Sylvia Tippmann</strong><br/>Data Scientist | <a href="http://sytpp.github.io">sytpp.github.io</a></td>
<td align="center"><img src="img/simon.png"/><br/><br/><strong>Simon Pamiés</strong><br/>Software Architect</td>
</tr>
</table>
</div>
</div>
<div class="container">
<div class="row">
<div class="col-lg-8 col-lg-offset-2">
<h2 class="text-center">How did this come about?</h2>
<p class="text-justify">This is what happens when computer-scientists mull over a humanistic question. "Does the right to be forgotten ruling amount to an inhibition of press freedom, or does it have merit as a protection of individuals’ right to privacy?" (Journalism & Society, 2014) - The answer to that, I concluded, is a cultural one, rather than a matter of facts.</p>
<p class="text-justify">What can be discussed as a matter of facts is its implementation. Google didn't seem to bother being terribly innovative about it and the <a href="https://www.google.com/advisorycouncil/">European Council Tour</a> mostly offered advise from a philosophical and legal angle. That's good but we figured an actual technical approach was missing. Over a couple of weeks we drew up a detailed, data-driven proposal for an implementation of the Right to be Forgotten on Google's side. It was intended to provide the company with a possible solution for this logistic challenge, and address its legal and image problems in Europe. Importantly, we proposed to make the decision process more democratic and transparent. Consulting with people in AI, app development, and marketing, gave us confidence that it is feasible to improve the status quo.</p>
<p class="text-justify">Despite all efforts (and a few contacts) it was impossible to reach the right person to address the proposal to. Nobody said pitching to Google was going to be easy. Digging deeper into all available sources, we discovered some data that was missing from the debate entirely and possibly why it was so difficult to pitch. By making this data publicly available in a visual way, we hope to reanimate an informed discussion and provide a common ground for speakers of all European languages to contribute and share data (and related insights) from their country. If you want to contribute, please <a href="https://github.com/sytpp/rtbf">fork this page</a> and add your language version!</p>
<p class="text-justify"><b>Eventually, we hope to bring our technical proposal forward, but let's have a discussion about the data first!</b></p>
<br><br>
<h2 class="text-center">Data Source</h2>
<p class="text-justify">The numeric data we refer to on this website was obtained from archived versions of Google's Transparency Report, available via Wayback Machine. You can find snap-shots of the website <a href="http://web.archive.org/web/*/http://www.google.com/transparencyreport/removals/europeprivacy/?hl=en">here</a> and <a href="http://web.archive.org/web/*/http://www.google.com/transparencyreport/removals/europeprivacy/?hl=en">here</a> (depending on your country settings you may see different ones).<br>
The data was not visualised on the front-end but available in the source code in JSON format under the variable name AGGREGATE_DATA. All snapshots we found before March 23rd 2015 do contain the breakdown of the data into issue types, while all snapshots after April 18th 2015 don't.<br><br>
<a href="view-source:http://web.archive.org/web/20150326090702/https://www.google.com/transparencyreport/removals/europeprivacy/">Link to data from March 23rd 2015</a>, used for this analysis.</p>
<br><br><br><br><br>
</div>
</div>
</div>
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement( o ),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-65139102-1', 'auto');
ga('send', 'pageview');
</script>
</body>
</html>