<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Here is a hort report on this experiment...</p>
<p>I started a week ago by searching OSM France tile server logs for
referer and checked manually if the map on the refering page was
correctly attributed.</p>
<p>This allowed me to create a short list of 20 entries of sites
using the french styled tiles and the humanitarian tiles (yes, it
is made by OSM France).</p>
<p><br>
</p>
<p>I then modified our nginx based proxy_cache configuration, to
redirect some tiles to an "attribution tile" only for the domain
in the list.</p>
<p>For two of them, I tweeted about it... the most visible one is
the moroco yellow page service, generating a little less than a
million daily tile requests on our servers.</p>
<p><a class="moz-txt-link-freetext" href="https://twitter.com/cq94/status/1234516075695525888">https://twitter.com/cq94/status/1234516075695525888</a></p>
<p>In less than 24 hours, the attribution appeared and I removed
them from the list.</p>
<p><a class="moz-txt-link-freetext" href="https://twitter.com/cq94/status/1234779931537739776">https://twitter.com/cq94/status/1234779931537739776</a></p>
<p><br>
</p>
<p>Then I included an email address in the attribution reminder
tile... and got emails back within a few hours.</p>
<p>Some were asking how to do the attribution, others telling me the
attribution was now ok and asking how to remove the reminder
tiles.</p>
<p>In my answers, I also remind that our tile service made by
volunteers on donated hardware is not unlimited and inviting them
to have a look at switch2osm to setup their own tile server or use
a commercial provider.<br>
</p>
<p>Up to now, nobody complained :)</p>
<p><br>
</p>
<p>Yesterday, I've started automating attribution checking using
selenium. For each referer, a python script loads the page,
searches for tiles, then looks for attribution text or link. The
result is stored in a postgresql database which allows to group
referers by url, hostname and ip.<br>
</p>
<p>The attribution percentage I currently see is around 70-80% which
is not that bad.</p>
<p>My next major step is to use the same technique to remind about
tile usage policy...<br>
</p>
<p><br>
</p>
<p>To do something similar on osm.org, a first step is to extract
referers from the cache logs, then use the automated attribution
check to evaluate the situation.<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Le 08/03/2020 à 01:52, Nuno Caldeira a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAK5cRsqs06QJQwBciWLqQWn7La-nqr2yJpuBbpJAE6uL2f_Uaw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">That would be a good option for those that use
third party providers of OSM. But to be honest, from my
experience I highly doubt that even corporate members of OSMF,
like Mapbox would do it, when their client Facebook (also
corporate member of OSMF) after one year and half, still has
maps with lack of attribution or attributed to HERE, when it's
clearly OSM. </div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, 8 Mar 2020, 00:46 Phil
Wyatt, <<a href="mailto:phil@wyatt-family.com"
moz-do-not-send="true">phil@wyatt-family.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I am sure
others may have seen this 'blacklist' implementation for
showing a reminder about attribution.<br>
<br>
<a href="https://twitter.com/cq94/status/1234528717604577282"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://twitter.com/cq94/status/1234528717604577282</a><br>
<br>
Worthy of consideration for <a
href="http://openstreetmap.org" rel="noreferrer noreferrer"
target="_blank" moz-do-not-send="true">openstreetmap.org</a>?<br>
<br>
Cheers - Phil</blockquote>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Christian Quest - OpenStreetMap France</pre>
</body>
</html>