diff options
author | Christian Mollekopf <chrigi_1@fastmail.fm> | 2017-09-13 12:42:31 +0200 |
---|---|---|
committer | Christian Mollekopf <chrigi_1@fastmail.fm> | 2017-09-13 12:42:31 +0200 |
commit | c12a9a09da59b9e418316dba02e6215cb55e47ee (patch) | |
tree | 05498d9a42e399bcca787f40c1fc473fb09e680e /tests/threaddata/thread1 | |
parent | 55fe06979ceebe67553135b43aa47e70d931304b (diff) | |
parent | ebdb89b8bb482bbb5ecd544c3d38bef35fc7d820 (diff) | |
download | sink-c12a9a09da59b9e418316dba02e6215cb55e47ee.tar.gz sink-c12a9a09da59b9e418316dba02e6215cb55e47ee.zip |
Merge commit 'ebdb89b8bb482bbb5ecd544c3d38bef35fc7d820'v0.4.0
Diffstat (limited to 'tests/threaddata/thread1')
-rw-r--r-- | tests/threaddata/thread1 | 228 |
1 files changed, 228 insertions, 0 deletions
diff --git a/tests/threaddata/thread1 b/tests/threaddata/thread1 new file mode 100644 index 0000000..8b72901 --- /dev/null +++ b/tests/threaddata/thread1 | |||
@@ -0,0 +1,228 @@ | |||
1 | Return-Path: <kde-community-bounces@kde.org> | ||
2 | Received: from imapb010.mykolab.com ([unix socket]) | ||
3 | by imapb010.mykolab.com (Cyrus 2.5.10-49-g2e214b4-Kolab-2.5.10-8.1.el7.kolab_14) with LMTPA; | ||
4 | Sun, 13 Aug 2017 11:50:30 +0200 | ||
5 | X-Sieve: CMU Sieve 2.4 | ||
6 | Received: from int-mx002.mykolab.com (unknown [10.9.13.2]) | ||
7 | by imapb010.mykolab.com (Postfix) with ESMTPS id E79C512C084C4 | ||
8 | for <christian@mailqueue.ch>; Sun, 13 Aug 2017 11:50:29 +0200 (CEST) | ||
9 | Received: from mx.kolabnow.com (unknown [10.9.4.1]) | ||
10 | by int-mx002.mykolab.com (Postfix) with ESMTPS id BE41F2329 | ||
11 | for <christian@mailqueue.ch>; Sun, 13 Aug 2017 11:50:29 +0200 (CEST) | ||
12 | X-Virus-Scanned: amavisd-new at mykolab.com | ||
13 | Authentication-Results: ext-mx-in001.mykolab.com (amavisd-new); | ||
14 | dkim=pass (1024-bit key) header.d=kde.org | ||
15 | X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 | ||
16 | Received: from forward2-smtp.messagingengine.com (forward2-smtp.messagingengine.com [66.111.4.226]) | ||
17 | by ext-mx-in001.mykolab.com (Postfix) with ESMTPS id 5614B11BB | ||
18 | for <christian@mailqueue.ch>; Sun, 13 Aug 2017 11:50:08 +0200 (CEST) | ||
19 | Received: from mailredirect.nyi.internal (imap36.nyi.internal [10.202.2.86]) | ||
20 | by mailforward.nyi.internal (Postfix) with ESMTP id E9026D1C6 | ||
21 | for <christian@mailqueue.ch>; Sun, 13 Aug 2017 05:50:06 -0400 (EDT) | ||
22 | Received: by mailredirect.nyi.internal (Postfix, from userid 501) | ||
23 | id D95328E3AC; Sun, 13 Aug 2017 05:50:06 -0400 (EDT) | ||
24 | Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) | ||
25 | by sloti36d2t28 (Cyrus fastmail-fmjessie44745-15358-git-fastmail-15358) with LMTPA; | ||
26 | Sun, 13 Aug 2017 05:50:06 -0400 | ||
27 | X-Cyrus-Session-Id: sloti36d2t28-2961984-1502617806-2-9300763073201928650 | ||
28 | X-Sieve: CMU Sieve 3.0 | ||
29 | X-Spam-known-sender: no | ||
30 | X-Orig-Spam-score: 0.0 | ||
31 | X-Spam-hits: BAYES_20 -0.001, RCVD_IN_DNSWL_MED -2.3, RP_MATCHES_RCVD -0.001, | ||
32 | SPF_PASS -0.001, LANGUAGES en, BAYES_USED global, SA_VERSION 3.4.0 | ||
33 | X-Spam-source: IP='46.4.96.248', Host='postbox.kde.org', Country='DE', FromHeader='org', | ||
34 | MailFrom='org' | ||
35 | X-Spam-charsets: plain='us-ascii' | ||
36 | X-Attached: signature.asc | ||
37 | X-Resolved-to: chrigi_1@fastmail.fm | ||
38 | X-Delivered-to: chrigi_1@fastmail.fm | ||
39 | X-Mail-from: kde-community-bounces@kde.org | ||
40 | Received: from mx4 ([10.202.2.203]) | ||
41 | by compute1.internal (LMTPProxy); Sun, 13 Aug 2017 05:50:06 -0400 | ||
42 | Authentication-Results: mx4.messagingengine.com; | ||
43 | dkim=pass (1024-bit rsa key sha256) header.d=kde.org header.i=@kde.org header.b=aAtxmD+3; | ||
44 | dmarc=none (p=none;has-list-id=yes) header.from=kde.org; | ||
45 | smime=temperror; | ||
46 | spf=pass smtp.mailfrom=kde-community-bounces@kde.org smtp.helo=postbox.kde.org | ||
47 | Received-SPF: pass | ||
48 | (kde.org: 46.4.96.248 is authorized to use 'kde-community-bounces@kde.org' in 'mfrom' identity (mechanism 'mx' matched)) | ||
49 | receiver=mx4.messagingengine.com; | ||
50 | identity=mailfrom; | ||
51 | envelope-from="kde-community-bounces@kde.org"; | ||
52 | helo=postbox.kde.org; | ||
53 | client-ip=46.4.96.248 | ||
54 | Received: from postbox.kde.org (postbox.kde.org [46.4.96.248]) | ||
55 | (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) | ||
56 | (No client certificate requested) | ||
57 | by mx4.messagingengine.com (Postfix) with ESMTPS | ||
58 | for <chrigi_1@fastmail.fm>; Sun, 13 Aug 2017 05:50:05 -0400 (EDT) | ||
59 | DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kde.org; s=default; | ||
60 | t=1502617803; bh=IzJP1FRz6gX2xTBV2xMDBc2KfNLK284LvmfZvBQHRwU=; | ||
61 | h=From:To:Subject:Date:Reply-To:List-Id:List-Unsubscribe: | ||
62 | List-Archive:List-Post:List-Help:List-Subscribe:From; | ||
63 | b=aAtxmD+3cXY913YngN6okQjxPwOn+T9Cw1Hl1NpSZ2E4VbNDeuQ9IVj6zCqeAZE6y | ||
64 | elk2GquLeHlXeLnygo2n5LQL6epM83pkS+1AWSHQI11mBDT5byLUrXX64hOSZ579jG | ||
65 | L6+jAJT8vcqnXZcGg5EjBQqYmFp4HLedW/xduUVg= | ||
66 | X-Original-To: kde-community@kde.org | ||
67 | X-Remote-Delivered-To: kde-community@localhost.kde.org | ||
68 | Received-SPF: Neutral (access neither permitted nor denied) identity=mailfrom; | ||
69 | client-ip=85.214.75.115; helo=h2670809.stratoserver.net; | ||
70 | envelope-from=vkrause@kde.org; receiver=kde-community@kde.org | ||
71 | Received: from h2670809.stratoserver.net (deltatauchi.de [85.214.75.115]) | ||
72 | by postbox.kde.org (Postfix) with ESMTP id 61C21A308E | ||
73 | for <kde-community@kde.org>; Sun, 13 Aug 2017 09:49:38 +0000 (UTC) | ||
74 | Received: from deltatauchi.de (ip5b403802.dynamic.kabel-deutschland.de | ||
75 | [91.64.56.2]) | ||
76 | by h2670809.stratoserver.net (Postfix) with ESMTPSA id 521BBF1A0104 | ||
77 | for <kde-community@kde.org>; Sun, 13 Aug 2017 11:49:07 +0200 (CEST) | ||
78 | From: Volker Krause <vkrause@kde.org> | ||
79 | To: kde-community@kde.org | ||
80 | Subject: Telemetry Policy | ||
81 | Date: Sun, 13 Aug 2017 11:47:28 +0200 | ||
82 | Message-ID: <2048912.XfIJe3ZSdj@vkpc5> | ||
83 | Organization: KDE | ||
84 | X-Face: rgzmh}R?iq<z7H#sc'l86vzjJ"{\d6`}N5x*9!HFBn`A^tnU?<Q%ruT(jt5PG1$td=GDXe | ||
85 | XsXW(lVZ%Z0.2|w-)y[+@HI})\pNZEMi/UY_D"; | ||
86 | tt:5C'5&O9_xAqO!$HA8Ks-5}uMz%`D "2{s`Mt$}N]I`0UI=0; | ||
87 | '4v"!]XgBET9Q%cB?\vr#1=5X3,[a3k@083{n9H0m~Ey5_5xOb; @06MoJe"3/Rfe[eki | ||
88 | MIME-Version: 1.0 | ||
89 | Content-Type: multipart/signed; boundary="nextPart1627232.ab0ruIHapE"; | ||
90 | micalg="pgp-sha1"; protocol="application/pgp-signature" | ||
91 | X-BeenThere: kde-community@kde.org | ||
92 | X-Mailman-Version: 2.1.16 | ||
93 | Precedence: list | ||
94 | Reply-To: informing about and discussing non-technical community topics | ||
95 | <kde-community@kde.org> | ||
96 | List-Id: informing about and discussing non-technical community topics | ||
97 | <kde-community.kde.org> | ||
98 | List-Unsubscribe: <https://mail.kde.org/mailman/options/kde-community>, | ||
99 | <mailto:kde-community-request@kde.org?subject=unsubscribe> | ||
100 | List-Archive: <http://mail.kde.org/pipermail/kde-community/> | ||
101 | List-Post: <mailto:kde-community@kde.org> | ||
102 | List-Help: <mailto:kde-community-request@kde.org?subject=help> | ||
103 | List-Subscribe: <https://mail.kde.org/mailman/listinfo/kde-community>, | ||
104 | <mailto:kde-community-request@kde.org?subject=subscribe> | ||
105 | Errors-To: kde-community-bounces@kde.org | ||
106 | Sender: "kde-community" <kde-community-bounces@kde.org> | ||
107 | |||
108 | --nextPart1627232.ab0ruIHapE | ||
109 | Content-Transfer-Encoding: 7Bit | ||
110 | Content-Type: text/plain; charset="us-ascii" | ||
111 | |||
112 | Hi, | ||
113 | |||
114 | during the KUserFeedback BoF at Akademy there was quite some interest in | ||
115 | collecting telemetry data in KDE applications. But before actually | ||
116 | implementing that we agreed to define the rules under which we would want to | ||
117 | do that. I've tried to put the input we collected during Akademy into proper | ||
118 | wording below. What do you think? Did I miss anything? | ||
119 | |||
120 | Regards, | ||
121 | Volker | ||
122 | |||
123 | |||
124 | # Telemetry Policy Draft | ||
125 | |||
126 | Application telemetry data can be a valuable tool for tailoring our products | ||
127 | to the needs of our users. The following rules define how KDE collects and | ||
128 | uses such application telemetry data. As privacy is of utmost importance to | ||
129 | us, the general rule of thumb is to err on the side of caution here. Privacy | ||
130 | always trumps any need for telemetry data, no matter how legitimate. | ||
131 | |||
132 | These rules apply to all products released by KDE. | ||
133 | |||
134 | ## Transparency | ||
135 | |||
136 | We provide detailed information about the data that is going to be shared, in | ||
137 | a way that: | ||
138 | - is easy to understand | ||
139 | - is precise and complete | ||
140 | - is available locally without network connectivity | ||
141 | |||
142 | Any changes or additions to the telemetry functionality of an application will | ||
143 | be highlighted in the corresponding release announcement. | ||
144 | |||
145 | ## Control | ||
146 | |||
147 | We give the user full control over what data they want to share with KDE. In | ||
148 | particular: | ||
149 | - application telemetry is always opt-in, that is off by default | ||
150 | - application telemetry settings can be changed at any time, and are provided | ||
151 | as prominent in the application interface as other application settings | ||
152 | - applications honor system-wide telemetry settings where they exist (global | ||
153 | "kill switch") | ||
154 | - we provide detailed documentation about how to control the application | ||
155 | telemetry system | ||
156 | |||
157 | In order to ensure control over the data after it has been shared with KDE, | ||
158 | applications will only transmit this data to KDE servers, that is servers | ||
159 | under the full control of the KDE sysadmin team. | ||
160 | |||
161 | We will provide a designated contact point for users who have concerns about | ||
162 | the data they have shared with KDE. While we are willing to delete data a user | ||
163 | no longer wants to have shared, it should be understood that the below rules | ||
164 | are designed to make identification of data of a specific user impossible, and | ||
165 | thus a deletion request impractical. | ||
166 | |||
167 | ## Anonymity | ||
168 | |||
169 | We do not transmit data that could be used to identify a specific user. In | ||
170 | particular: | ||
171 | - we will not use any unique device, installation or user id | ||
172 | - data is stripped of any unnecessary detail and downsampled appropriately | ||
173 | before sharing to avoid fingerprinting | ||
174 | - network addresses (which are exposed inevitably as part of the data | ||
175 | transmission) are not stored together with the telemetry data, and must only | ||
176 | be stored or used to the extend necessary for abuse counter-measures | ||
177 | |||
178 | ## Minimalism | ||
179 | |||
180 | We only track the bare minimum of data necessary to answer specific questions, | ||
181 | we do not collect data preemptively or for exploratory research. In | ||
182 | particular, this means: | ||
183 | - collected data must have a clear purpose | ||
184 | - data is downsampled to the maximum extend possible at the source | ||
185 | - relevant correlations between individual bits of data should be computed at | ||
186 | the source whenever possible | ||
187 | - data collection is stopped once corresponding question has been answered | ||
188 | |||
189 | ## Privacy | ||
190 | |||
191 | We will never transmit anything containing user content, or even just hints at | ||
192 | possible user content such as e.g. file names, URLs, etc. | ||
193 | |||
194 | We will only ever track: | ||
195 | - system information that are specific to the installation/environment, but | ||
196 | independent of how the application/machine/installation is actually used | ||
197 | - statistical usage data of an installation/application | ||
198 | |||
199 | ## Compliance | ||
200 | |||
201 | KDE only releases products capable of acquiring telemetry data if compliance | ||
202 | with these rules has been established by a public review on [kde-core-devel| | ||
203 | kde-community]@kde.org from at least two reviewers. The review has to be | ||
204 | repeated for every release if changes have been made to how/what data is | ||
205 | collected. | ||
206 | |||
207 | Received data is regularly reviewed for violations of these rules, in | ||
208 | particular for data that is prone to fingerprinting. Should such violations be | ||
209 | found, the affected data will be deleted, and data recording will be suspended | ||
210 | until compliance with these rules has been established again. In order to | ||
211 | enable reviewing of the data, every KDE contributor with a developer account | ||
212 | will have access to all telemetry data gathered by any KDE product. | ||
213 | |||
214 | --nextPart1627232.ab0ruIHapE | ||
215 | Content-Type: application/pgp-signature; name="signature.asc" | ||
216 | Content-Description: This is a digitally signed message part. | ||
217 | Content-Transfer-Encoding: 7Bit | ||
218 | |||
219 | -----BEGIN PGP SIGNATURE----- | ||
220 | |||
221 | iF0EABECAB0WIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCWZAgMAAKCRB/lszWTRLS | ||
222 | Ry5WAJ9+8r8e7IFPh54YBsEkisE3+dNs8QCfY+0b0jcYPVP1HdpsTZVoh33JfhU= | ||
223 | =v6cZ | ||
224 | -----END PGP SIGNATURE----- | ||
225 | |||
226 | --nextPart1627232.ab0ruIHapE-- | ||
227 | |||
228 | |||