<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>The problem with this thread is that it is conflating different
(but a bit related) things.</p>
<p>- missing or less than perfect attribution,<br>
</p>
<p>- corporate messaging about OpenStreetMap (or more the lack of
it).<br>
</p>
<p>As to the first point in general we are just arguing about the
form, not the principle. We have only one case that I'm aware of,
in which a publisher is claiming that they do not need to provide
attribution, and we are pursing that with legal means. <br>
</p>
<p>It is however important to realize that their are limits to
copyright and that for example lots of the "non-attribution" in
the states is likely permissible fair use under US laws. It would
still be good form to provide attribution, but it isn't something
we can enforce and getting upset about such use is really just a
tremendous waste of time. <br>
</p>
<p>As to the 2nd point, yes it might be annoying that we don't get
more positive corporate messaging around the use of OpenStreetMap,
particularly when the companies in question wouldn't actually
exist without OSM, but it isn't a legal or attribution question
and should be kept separate. Relying on third parties that are
mainly beholden to money to do messaging on our behalf is a very
bad idea in any case, the responsibility for positive messaging is
clearly part of the remit of the OSMF.</p>
<p>Simon<br>
</p>
<div class="moz-cite-prefix">Am 31.10.2019 um 10:41 schrieb Nuno
Caldeira:<br>
</div>
<blockquote type="cite"
cite="mid:CAK5cRspQzug4wUedXJhpAKNqj8w=1W--1HaWOpZFMF_7LGuGGQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">do a search for Strava on social media images, on
twitter as examples:
<div dir="auto"><br>
</div>
<div dir="auto"><a
href="https://twitter.com/MissJKirby/status/1189164486252515333?s=09"
moz-do-not-send="true">https://twitter.com/MissJKirby/status/1189164486252515333?s=09</a></div>
<div dir="auto"><br>
</div>
<div dir="auto"><a
href="https://twitter.com/boorapong88/status/1188767309357142016?s=09"
moz-do-not-send="true">https://twitter.com/boorapong88/status/1188767309357142016?s=09</a></div>
<div dir="auto"><br>
</div>
<div dir="auto"><a
href="https://twitter.com/dai_walters/status/1188488659089141760?s=09"
moz-do-not-send="true">https://twitter.com/dai_walters/status/1188488659089141760?s=09</a></div>
<div dir="auto"><br>
</div>
<div dir="auto">só either everyone crops the image or there's
something wrong. </div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">following your mindset, we should blame the map
provider (Mapbox) and not the company that uses the maos. Does
this apply to Facebook too? As Mapbox is a corporate member of
OSMF and several employees of theirs are members of board or
working groups, that shouldn't be to hard to fix the lack of
attribution, right? </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, 31 Oct 2019, 09:28
Jeffrey Friedl, <<a href="mailto:jfriedl@yahoo.com"
moz-do-not-send="true">jfriedl@yahoo.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
<br>
<br>
<br>
> > And the hypocrisy goes on. "Strava launches gorgeous
new outdoor maps" <a
href="https://blog.mapbox.com/strava-launches-gorgeous-new-outdoor-maps-977c74cf37f9"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://blog.mapbox.com/strava-launches-gorgeous-new-outdoor-maps-977c74cf37f9</a><br>
><br>
> I'm not sure what you're reporting, but the maps all
have "© Mapbox © OpenStreetMap" in the lower-left<br>
> corner. (Perhaps they were cut off in some of the
screenshots in news coverage, but the actual maps in<br>
> the Strava app and on their web site all have this
attribution.) I suppose that they could use a slightly<br>
> stronger background shadow, to create more contrast
when the map behind the attribution is light.<br>
><br>
><br>
> that is not true.<br>
<br>
WHAT is not true? Why can't you be specific?<br>
<br>
> <a
href="https://twitter.com/mastermen/status/1127672128797663239?s=09"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://twitter.com/mastermen/status/1127672128797663239?s=09</a><br>
<br>
That's a half year ago, showing an edited screen capture. What
relevence is to this discussion?<br>
<br>
> from the moment they use OSM they agreed with it's terms<br>
<br>
"They" being Strava? I don't beleve that Strava uses, or has
ever used, OSM data.<br>
I'm pretty sure that Strava is a customer of Mapbox, and it's
*Mapbox* that uses OSM data<br>
and generates images that Strava displays. If Mapbox is not
putting attributions properly,<br>
complain to/about them.<br>
<br>
Jeffrey<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
talk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk">https://lists.openstreetmap.org/listinfo/talk</a>
</pre>
</blockquote>
</body>
</html>