<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>So how about this map? Is one click still a lack of attribution?<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><a href="https://www.rolexsydneyhobart.com/tracker/">https://www.rolexsydneyhobart.com/tracker/</a><span style='mso-fareast-language:EN-US'><o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Nuno Caldeira <nunocapelocaldeira@gmail.com> <br><b>Sent:</b> Thursday, 26 December 2019 6:17 AM<br><b>To:</b> · Michael Medina <recycleoregon@gmail.com><br><b>Cc:</b> OpenStreetMap talk mailing list <talk@openstreetmap.org><br><b>Subject:</b> Re: [OSM-talk] [Osmf-talk] Attribution guideline status update<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>doesn't surprise me. check this <a href="https://docs.mapbox.com/mapbox-gl-js/example/attribution-position/">https://docs.mapbox.com/mapbox-gl-js/example/attribution-position/</a> plenty of space for visible attribution, well mapbox attribution is not hidden under an "i". I have reported another client of theirs that I have reached out to ask for attribution, which they understood, but still haven't fixed it. let's see if mapbox is in good will. <o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, 25 Dec 2019, 17:20 · Michael Medina, <<a href="mailto:recycleoregon@gmail.com">recycleoregon@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p class=MsoNormal>As a native English speaker this reads as complete stonewalling on Mapbox’s part. I don’t know why OSM doesn’t just file a DMCA complaint against Mapbox or deny them access. The OSM board should also not have to go through the regular help channel to get answers. Mapbox should escalate this issue to their top administrators. I know the board likes to play nice, but Mapbox isn’t playing nice so no reason to as far as I can tell. <o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Michael Medina <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, Dec 25, 2019 at 04:06 <<a href="mailto:talk-request@openstreetmap.org" target="_blank">talk-request@openstreetmap.org</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal>Send talk mailing list submissions to<br> <a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="https://lists.openstreetmap.org/listinfo/talk" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><br>or, via email, send a message with subject or body 'help' to<br> <a href="mailto:talk-request@openstreetmap.org" target="_blank">talk-request@openstreetmap.org</a><br><br>You can reach the person managing the list at<br> <a href="mailto:talk-owner@openstreetmap.org" target="_blank">talk-owner@openstreetmap.org</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of talk digest..."<br><br><br>Today's Topics:<br><br> 1. Re: [Osmf-talk] Attribution guideline status update<br> (Nuno Caldeira)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 24 Dec 2019 17:52:53 +0000<br>From: Nuno Caldeira <<a href="mailto:nunocapelocaldeira@gmail.com" target="_blank">nunocapelocaldeira@gmail.com</a>><br>To: Mateusz Konieczny <<a href="mailto:matkoniecz@tutanota.com" target="_blank">matkoniecz@tutanota.com</a>><br>Cc: joost schouppe <<a href="mailto:joost.schouppe@gmail.com" target="_blank">joost.schouppe@gmail.com</a>>, OSMF Talk<br> <<a href="mailto:osmf-talk@openstreetmap.org" target="_blank">osmf-talk@openstreetmap.org</a>>, OpenStreetMap talk mailing list<br> <<a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a>><br>Subject: Re: [OSM-talk] [Osmf-talk] Attribution guideline status<br> update<br>Message-ID: <<a href="mailto:ea8605f7-ac7d-040e-c38a-f80c2cbc8311@gmail.com" target="_blank">ea8605f7-ac7d-040e-c38a-f80c2cbc8311@gmail.com</a>><br>Content-Type: text/plain; charset="utf-8"; Format="flowed"<br><br>Hi Mateusz,<br><br><br>They don't. Here's all my email exchange with them from October 2018, <br>yes _*2018*_. it's more than enough with evidence and time to be fixed. <br><a href="https://drive.google.com/file/d/110XubCe0kd2HNtbqXS7U_vr44xyieaSt/view?usp=sharing" target="_blank">https://drive.google.com/file/d/110XubCe0kd2HNtbqXS7U_vr44xyieaSt/view?usp=sharing</a><br><br><br>On 24/12/2019 07:08, Mateusz Konieczny wrote:<br>> Have they responded with anything<br>> (except automatic reply) ?<br>><br>> Is there an assigned issue id?<br>><br>><br>> 23 Dec 2019, 21:32 by <a href="mailto:nunocapelocaldeira@gmail.com" target="_blank">nunocapelocaldeira@gmail.com</a>:<br>><br>> I sent this situation to Mapbox 10 months ago.<br>><br>> On Mon, 23 Dec 2019, 17:00 joost schouppe,<br>> <<a href="mailto:joost.schouppe@gmail.com" target="_blank">joost.schouppe@gmail.com</a> <mailto:<a href="mailto:joost.schouppe@gmail.com" target="_blank">joost.schouppe@gmail.com</a>>> wrote:<br>><br>><br>> As an xmas bonus, here's another Facebook company (via<br>> Mapbox), Snapchat that is using OSM without attribution<br>> requirements (funnily there's plenty of space for a<br>> reasonable and visible calculated mapbox logo and text).<br>> They probably don't know, nor that they have been asked to<br>> comply over a year ago, nor have agreed with the license<br>> in every aspect of it when stated using OSM data, nor read<br>> Mapbox TOS, or Mapbox been informed on these repeated<br>> offenders, nor read the multiples reports in mailing<br>> lists, nor that they had a employee that ran for OSMF board.<br>><br>> <a href="https://map.snapchat.com/" target="_blank">https://map.snapchat.com/</a><br>><br>> Let's continue to be hypocrites and pretend nothing is<br>> going on for over a year with these two companies that are<br>> corporate members of OSMF and should be the first ones to<br>> give examples. Enough with excuses.<br>><br>><br>> The Snapchat case is a pretty clear example of how not to do<br>> things. If there's space for Mapbox, there's space for<br>> OpenStreetMap. But I don't think Snapchat has anything to do<br>> with Facebook.<br>><br>> Phil, I hope you contacted them directly and not through Facebook.<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.openstreetmap.org/pipermail/talk/attachments/20191224/e4cbcf8f/attachment.htm" target="_blank">http://lists.openstreetmap.org/pipermail/talk/attachments/20191224/e4cbcf8f/attachment.htm</a>><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>talk mailing list<br><a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a><br><a href="https://lists.openstreetmap.org/listinfo/talk" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><br><br><br>------------------------------<br><br>End of talk Digest, Vol 184, Issue 39<br>*************************************<o:p></o:p></p></blockquote></div></div><p class=MsoNormal>_______________________________________________<br>talk mailing list<br><a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a><br><a href="https://lists.openstreetmap.org/listinfo/talk" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><o:p></o:p></p></blockquote></div></div></body></html>