Google’s GDPR consent requirements for publishers and advertisers, May 2018

6 Maggio 2018 ~ nemobis ~ Lascia un commento

There was a lot of discussion about the publishers’ reaction to certain requirements they got from Google in relation to the EU’s General Data Protection Regulation.

For reference, here’s the text Google sent on May 5, 2018 (presumably to all Google AdWords and Google AdSense users). https://www.cookiechoices.org/ got a revamp, too (only in English for now).

Dear Customer,

In August last year, we announced our commitment to comply with Europe’s new General Data Protection Regulation (GDPR). In March, we shared more about our GDPR policy, contract and product changes and today, we are sharing more details about solutions advertisers can use to gather consent, information about new publisher consent tools which may affect where your ads appear, consent approach for non-Google exchanges, as well as other important GDPR related updates that require your attention.

Consent solutions

We have updated cookiechoices.org with examples of consent language and available third party consent solutions. We have also updated our Help Center to provide more clarity on implementing our updated EU User Consent Policy.

Recommended action: Think through how you will collect consent from users across your sites and apps. You may wish to use your own consent mechanism or one of the solutions listed at cookiechoices.org.

New controls for publishers, and updates to exchange integrations, which may affect where your ads appear if you use third party ad serving and/or tracking:

Ad Technology Provider Controls:

We will shortly be launching Ad Technology Provider Controls for publishers using our advertising solutions (DFP/AdX, AdMob, AdSense).
Through these controls, publishers can choose the ad technology providers that will be supported to serve and measure ads on their sites and apps for users in the European Economic Area (EEA).
All providers listed have shared certain information that is required by the GDPR. You can encourage your provider to do the same (process guide) – this process is open to all ad tech providers.
For those publishers who don’t engage with the controls to choose their own list, we will apply a ‘commonly used’ list of Ad Technology Providers.
In practice, this means your campaigns will only serve for an ad impression in the EEA where the publisher supports the Ad Technology Providers you use.

Non-Personalized Ads:

We will also launch a Non-Personalized Ads solution (DFP/AdX, AdMob, AdSense) to enable publishers to present EEA users with a choice between personalized ads and non-personalized ads (or to choose to serve only non-personalized ads to all users in the EEA). Non-Personalized Ads are described in our Help Center.

Integrations with third party ad exchanges:

We will be working with third-party exchanges utilizing the IAB’s GDPR Transparency and Consent Framework and those subject to our EU User Consent Policy.

Recommended actions: Review your use of third-party ad servers and/or pixels with vendors that are not part of our Ad Technology Provider Controls to avoid downtime in campaign serving, measurement and/or user lists.

Other details that require your attention:

If you use Google Analytics 360 or DoubleClick: Please review and/or accept data processing terms available in each account you manage.
If you use Google Analytics (Standard or 360): Please review the data retention controls that allow you to manage how long your user and event data is held on our servers. Starting May 25, we will process data deletions based on your settings.
If you use third-party ad serving and/or tracking on YouTube: Please review our recent notices with re-trafficking instructions for campaigns impacted by both limiting the number of third party measurement vendors on YouTube globally as well as suspension of support for third party ad serving in the EEA.
If you use Data Transfer: Note we will be redacting User and Partner IDs in data transfer files for EEA users from May 25. Your account teams will contact you for alternative solutions.

Find out more

If you have any questions on this update, please reach out to your account teams or contact us via In-Product Help tools.

Sincerely,
The Google Team

Google Ireland Ltd, Gordon House, Barrow Street, Dublin 4, Ireland.

You have received this mandatory email service announcement to update you about important changes to your Google product or account.

example-image1

WiFi on Finnish VR InterCity train

14 aprile 201714 aprile 2017 ~ nemobis ~ Lascia un commento

And now for comparison, some quick tests of the open train wifi from around Lahti in a “working compartment” (seats 1–7, coach 1) of an InterCity 5 operated by VR in Finland. Feels quite decent. (Bicycle transport is also good on this train.)

WiFi junassa (VR) ja latenssi.

Access point

$ iwconfig

wls1      IEEE 802.11  ESSID:"VR-junaverkko"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 68:99:CD:B9:30:10
          Bit Rate=104 Mb/s   Tx-Power=15 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=70/70  Signal level=-29 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:844   Missed beacon:0

$ uname -a
Linux x200s 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Connection to IRC server

Good enough for SSH not to be disconnected, but over 15 % packet loss and 500 ms latency with quite some jitter (judging from StDev).

$ mtr -w -c 100 kapsi.fi
Start: Fri Apr 14 14:02:31 2017
HOST: x200s                             Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- gateway                            0.0%   100    6.7  41.3   2.8 419.0  78.9
  2.|-- 164.5.101.168                     14.0%   100  352.5 551.0  83.5 1144. 251.5
  3.|-- 10.25.0.0                         99.0%   100  917.7 917.7 917.7 917.7   0.0
  4.|-- 83.150.93.45                      54.0%   100  21042 21042 20240 22463 486.5
  5.|-- rtr1-te1-3.lau.hel.fi.nblnet.com  13.0%   100  939.9 742.0  67.9 1209. 272.3
  6.|-- rtr1-po4.ipo.esp.fi.nblnet.com     8.0%   100   42.9 195.6  25.2 986.7 216.5
  7.|-- rtr2-po3.pit.hel.fi.nblnet.com    12.0%   100  664.1 580.7 119.2 1408. 278.1
  8.|-- pertr2-be10.pit.hel.fi.nblnet.com  9.0%   100  932.1 726.0  90.2 1363. 300.8
  9.|-- crtr1-v1329.pit.hel.fi.nblnet.com 15.2%    99  863.8 697.7 110.4 1266. 275.4
 10.|-- kapsi.fi                          17.2%    99  633.7 555.1  65.2 1240. 306.8

HTTP connection

Connnection Times (ms)
Server Software:		Apache
Server Hostname:		http://www.ripe.net
Server Port:		443
Document Path:		/
Document Length:		88455 bytes
Concurrency Level:		1
Time taken for tests:		94.474 seconds
Complete requests:		25
Failed requests:		0
Total transferred:		2219825 bytes
HTML transferred:		2211375 bytes
Requests per second:		0.26
Transfer rate:		22.95 kb/s received
	min	avg	max
Connect:	245	1142	2251
Processing:	617	2636	11159
Total:	862	3778	13410

Connessione Wi-Fi di Italo

8 aprile 2017 ~ nemobis ~ Lascia un commento

Fino a qualche tempo fa, la connessione a internet su Italotreno NTV risultava sempre inaffidabile per me, tanto da rinunciare a usarla.

Oggi, alle ore 8, a 300 km/h fra le nebbie milanesi, nella carrozza 8 quasi tutto vuota del Milano-Napoli, mi è andata meglio. Usare mosh per IRC comunque non guasta.

Latenza verso dominio IRC

Connnection Times (ms)
Server Software:		Apache/2.2.22
Server Hostname:		http://www.kapsi.fi
Server Port:		443
Document Path:		/
Document Length:		10256 bytes
Concurrency Level:		1
Time taken for tests:		20.798 seconds
Complete requests:		25
Failed requests:		0
Total transferred:		263525 bytes
HTML transferred:		256400 bytes
Requests per second:		1.20
Transfer rate:		12.37 kb/s received
	min	avg	max
Connect:	379	642	1813
Processing:	117	189	223
Total:	496	831	2036

Sito HTTPS

Connnection Times (ms)
Server Software:		Apache
Server Hostname:		http://www.ripe.net
Server Port:		443
Document Path:		/
Document Length:		88093 bytes
Concurrency Level:		1
Time taken for tests:		29.385 seconds
Complete requests:		25
Failed requests:		0
Total transferred:		2210775 bytes
HTML transferred:		2202325 bytes
Requests per second:		0.85
Transfer rate:		73.47 kb/s received
	min	avg	max
Connect:	257	367	1272
Processing:	353	808	6933
Total:	610	1175	8205

Scaricamento video da Wikimedia Commons

Qualcuno poco saggiamente gradisce effettuare anche operazioni piú pesanti in treno… Vediamo. (Qui siamo fra Reggio-Emilia e Bologna, la carrozza si è riempita di un gruppo di pensionati in visita a Roma. Senz’altro non sono tutti attaccati a Instagram.)

This is ApacheBench, Version 2.3 <$Revision: 1757674 $> 
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ 
Licensed to The Apache Software Foundation, http://www.apache.org/ 


apr_pollset_poll: The timeout specified has expired (70007)
Total of 4 requests completed

Ci sta. 😉

Appunti scettici dai beni comuni

Tecnologia