<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/tag/opacite">
<title>Public marks with tag opacite</title>
<description>Public marks with tag opacite</description>
<link>http://blogmarks.net/marks/tag/opacite</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058581852"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058512194"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058383869"/>
<rdf:li resource="http://blogmarks.net/api/user/LuciferX/mark/1419778"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058581852">
<title>Official Google Mobile Blog: Google Latitude, now with Location History &amp; Alerts</title>
<link>http://googlemobile.blogspot.com/2009/11/google-latitude-now-with-location.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;People also want to know when their friends were nearby, but it's not always convenient to keep checking Latitude to see if a friend has recently shown up near you. After working on this for a while, we realized it wasn't as straightforward as sending a notification every time Latitude friends were near each other. Imagine that you're Latitude friends with your roommate or co-workers. It would get pretty annoying to get a text message every single time you walked in the door at home or pulled into work. To avoid this, we decided to make Location Alerts smarter by requiring that you also enable Location History. Using your past location history, Location Alerts can recognize your regular, routine locations and not create alerts when you're at places like home or work. Alerts will only be sent to you and any nearby friends when you're either at an unusual place or at a routine place at an unusual time. Keep in mind that it may take up to a week to learn your &quot;unusual&quot; locations and start sending alerts.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-15T00:01:29Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>opacite, geolocation</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://googlemobile.blogspot.com/2009/11/google-latitude-now-with-location.html"><img border="0" src="http://blogmarks.net/screenshots/2009/11/15/5d1fdef88702c870473f41752d1a6af7.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://googlemobile.blogspot.com/2009/11/google-latitude-now-with-location.html">Official Google Mobile Blog: Google Latitude, now with Location History &amp; Alerts</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>People also want to know when their friends were nearby, but it's not always convenient to keep checking Latitude to see if a friend has recently shown up near you. After working on this for a while, we realized it wasn't as straightforward as sending a notification every time Latitude friends were near each other. Imagine that you're Latitude friends with your roommate or co-workers. It would get pretty annoying to get a text message every single time you walked in the door at home or pulled into work. To avoid this, we decided to make Location Alerts smarter by requiring that you also enable Location History. Using your past location history, Location Alerts can recognize your regular, routine locations and not create alerts when you're at places like home or work. Alerts will only be sent to you and any nearby friends when you're either at an unusual place or at a routine place at an unusual time. Keep in mind that it may take up to a week to learn your "unusual" locations and start sending alerts.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opacite">opacite</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geolocation">geolocation</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058581852">Copy</a> | 
<a href="http://blogmarks.net/link/3408172">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058512194">
<title>Cocoa with Love: WhereIsMyMac, a Snow Leopard CoreLocation project</title>
<link>http://cocoawithlove.com/2009/09/whereismymac-snow-leopard-corelocation.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;In Snow Leopard, you can ask for the computer's location. Without a GPS, how accurate could that be? The answer in my case is: very accurate. In this post, I'll show you how to write a CoreLocation app for the Mac that shows the current location in Google Maps, so you can see exactly where your computer thinks it is.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-21T23:11:48Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>opacite, corelocation, cocoa, macosx, geolocation</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://cocoawithlove.com/2009/09/whereismymac-snow-leopard-corelocation.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/21/75d5e96cdf8ef363a69c0e1fda7b6a11.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://cocoawithlove.com/2009/09/whereismymac-snow-leopard-corelocation.html">Cocoa with Love: WhereIsMyMac, a Snow Leopard CoreLocation project</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>In Snow Leopard, you can ask for the computer's location. Without a GPS, how accurate could that be? The answer in my case is: very accurate. In this post, I'll show you how to write a CoreLocation app for the Mac that shows the current location in Google Maps, so you can see exactly where your computer thinks it is.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opacite">opacite</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/corelocation">corelocation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cocoa">cocoa</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/macosx">macosx</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geolocation">geolocation</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058512194">Copy</a> | 
<a href="http://blogmarks.net/link/3349506">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058383869">
<title>Michael(tm) Smith » On privacy protection in Web applications and browser APIs</title>
<link>http://sideshowbarker.net/2009/06/22/lbs-privacy/#comment-527</link>
<description>&lt;blockquote&gt;&lt;p&gt;I feel a lot of anger and frustration in this list.&lt;/p&gt;&lt;p&gt;Some of the items seem fine to me. I would not have written them like this ;). I disagree strongly with the last one, not because of the rationale but the form. It’s an unproven affirmation. There will be cases where it will be indeed the case and some not. :)&lt;/p&gt;&lt;p&gt;About geolocation privacy, the issue has hit the fan already ;) Advertising the user’s location is one way to make aware the user (or users in developping countries) of a mobile device. Blocking access to the location is *not always* a solution either. Sometimes the solution will be in how long the data can be kept, sometimes the solution will be in how the data will be used.&lt;/p&gt;&lt;p&gt;Repeat after me 1000 times: It is not a privacy issue, but a lack (or very thin) opacity issue. The network makes the access to information very quick and easy. There’s no need or no use to block it. There is need to be able to slow down the stream at will.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-06-21T23:06:47Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>opacite, mobile, geolocation, societé</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://sideshowbarker.net/2009/06/22/lbs-privacy/#comment-527"><img border="0" src="http://blogmarks.net/screenshots/2009/06/21/738a6b440cd4d65f96dbe497c336cbb7.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://sideshowbarker.net/2009/06/22/lbs-privacy/#comment-527">Michael(tm) Smith » On privacy protection in Web applications and browser APIs</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>I feel a lot of anger and frustration in this list.</p><p>Some of the items seem fine to me. I would not have written them like this ;). I disagree strongly with the last one, not because of the rationale but the form. It’s an unproven affirmation. There will be cases where it will be indeed the case and some not. :)</p><p>About geolocation privacy, the issue has hit the fan already ;) Advertising the user’s location is one way to make aware the user (or users in developping countries) of a mobile device. Blocking access to the location is *not always* a solution either. Sometimes the solution will be in how long the data can be kept, sometimes the solution will be in how the data will be used.</p><p>Repeat after me 1000 times: It is not a privacy issue, but a lack (or very thin) opacity issue. The network makes the access to information very quick and easy. There’s no need or no use to block it. There is need to be able to slow down the stream at will.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opacite">opacite</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mobile">mobile</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geolocation">geolocation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/societ%25C3%25A9">societé</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058383869">Copy</a> | 
<a href="http://blogmarks.net/link/3248203">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/LuciferX/mark/1419778">
<title>Peut-être une réponse ?</title>
<link>http://www.peutetreunereponse.net/</link>
<description>Comme vous, j ai été confronté à quelques problèmes de CSS, d HTML, de javascript ou de gestion intrinsèque de notre hébérgeur chéri. Ce blog à pour but de vous aider à les résoudre.</description>
<dc:date>2006-12-21T11:00:38Z</dc:date>
<dc:author>LuciferX</dc:author>
<dc:subject>css, html, javascript, fckeditor, menu, deroulant, banniere, opacite, design, webdesign</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.peutetreunereponse.net/"><img border="0" src="http://blogmarks.net/screenshots/2008/08/08/938532560ddb56e54a141ff0be73f55c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.peutetreunereponse.net/">Peut-être une réponse ?</a></h4>
 
by <a href="http://blogmarks.net/user/LuciferX">LuciferX</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/496939">17 other(s)</a> 
<p class="description">Comme vous, j ai été confronté à quelques problèmes de CSS, d HTML, de javascript ou de gestion intrinsèque de notre hébérgeur chéri. Ce blog à pour but de vous aider à les résoudre.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fckeditor">fckeditor</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/menu">menu</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/deroulant">deroulant</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/banniere">banniere</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opacite">opacite</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/design">design</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdesign">webdesign</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1419778">Copy</a> | 
<a href="http://blogmarks.net/link/496939">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>