<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Privacy on HTML5 in 24 Hours</title>
    <link>https://www.html5in24hours.com/tags/privacy/</link>
    <description>Privacy on HTML5 in 24 Hours</description>
    <generator>Hugo</generator>
    <language>en-us</language><copyright>Jennifer Kyrnin</copyright><lastBuildDate>Sat, 09 Jul 2011 04:33:21 +0000</lastBuildDate>
    <atom:link href="https://www.html5in24hours.com/tags/privacy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GeoLocation versus &#34;personalized advertising&#34;</title>
      <link>https://www.html5in24hours.com/posts/geolocation-versus-personalized-advertising/</link>
      <pubDate>Sat, 09 Jul 2011 04:33:21 +0000</pubDate>
      <guid>https://www.html5in24hours.com/posts/geolocation-versus-personalized-advertising/</guid><description>&lt;p&gt;I&amp;rsquo;m writing about GeoLocation right now, and what interests me is that the specification requires that the browser ask permission before getting location data. That&amp;rsquo;s great.&lt;/p&gt;&#xA;&lt;p&gt;But what I find interesting is that to use GeoLocation, we web designers have to ask permission. But when it comes to serving &amp;ldquo;personalized&amp;rdquo; advertising, apparently no permission is needed.&lt;/p&gt;&#xA;&lt;p&gt;The only saving grace is that the ads tend to use IP addresses that puts my location as &amp;ldquo;Bothell, WA&amp;rdquo; which is 10-15 miles away from where I really am located.&lt;/p&gt;&#xA;</description>
    </item>
  </channel>
</rss>
