<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for Mosuki blog</title>
	<atom:link href="http://blog.mosuki.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.mosuki.com</link>
	<description>Spend more time with your friends.</description>
	<pubDate>Thu, 20 Nov 2008 09:38:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on Goodbye, surrealist hacker-chic by Mosuki blog &#187; Relational databases and free-form data</title>
		<link>http://blog.mosuki.com/20/goodbye-surrealist-hacker-chic#comment-2159</link>
		<dc:creator>Mosuki blog &#187; Relational databases and free-form data</dc:creator>
		<pubDate>Tue, 18 Mar 2008 23:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mosuki.com/20/goodbye-surrealist-hacker-chic#comment-2159</guid>
		<description>This power lets us implement major features that we didn&#8217;t plan for originally, like adding iCalendar feeds, discussion forums, scenes, places, and a myriad of object-specific user preferences to the site.</description>
		<content:encoded><![CDATA[<p>This power lets us implement major features that we didn&#8217;t plan for originally, like adding iCalendar feeds, discussion forums, scenes, places, and a myriad of object-specific user preferences to the site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Local events on Mosuki by ryssa</title>
		<link>http://blog.mosuki.com/47/local-events-on-mosuki#comment-1251</link>
		<dc:creator>ryssa</dc:creator>
		<pubDate>Thu, 04 Oct 2007 00:53:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mosuki.com/47/local-events-on-mosuki#comment-1251</guid>
		<description>Fantastic!  That seems like a workable radius for now, and probably the one I'll end up with even after you add the ability to pick.  You guys are doing that "smart" thing again.</description>
		<content:encoded><![CDATA[<p>Fantastic!  That seems like a workable radius for now, and probably the one I&#8217;ll end up with even after you add the ability to pick.  You guys are doing that &#8220;smart&#8221; thing again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Local events on Mosuki by brainsik</title>
		<link>http://blog.mosuki.com/47/local-events-on-mosuki#comment-1250</link>
		<dc:creator>brainsik</dc:creator>
		<pubDate>Wed, 03 Oct 2007 18:09:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mosuki.com/47/local-events-on-mosuki#comment-1250</guid>
		<description>For San Francisco residents, 80 miles will show you everything in the Bay Area, but not as far as Sacramento. One exception is any event posted to a scene you are in will always show up. For example, if someone posts a beer festival in Sacramento to the &lt;a href="http://mosuki.com/scene?id=~ckcqgswhm7bkmm" rel="nofollow"&gt;Beer scene&lt;/a&gt;, you'll see it in your event lists.

In the future, we'll be providing some tools on the event lists so users can change what shows up.

.:. jeremy</description>
		<content:encoded><![CDATA[<p>For San Francisco residents, 80 miles will show you everything in the Bay Area, but not as far as Sacramento. One exception is any event posted to a scene you are in will always show up. For example, if someone posts a beer festival in Sacramento to the <a href="http://mosuki.com/scene?id=~ckcqgswhm7bkmm" rel="nofollow">Beer scene</a>, you&#8217;ll see it in your event lists.</p>
<p>In the future, we&#8217;ll be providing some tools on the event lists so users can change what shows up.</p>
<p>.:. jeremy</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Local events on Mosuki by glyphobet</title>
		<link>http://blog.mosuki.com/47/local-events-on-mosuki#comment-1249</link>
		<dc:creator>glyphobet</dc:creator>
		<pubDate>Wed, 03 Oct 2007 17:16:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mosuki.com/47/local-events-on-mosuki#comment-1249</guid>
		<description>Right now the range is fixed at 80 miles.  (That seems really big, but keep in mind that  before this change, Mosuki showed you &lt;em&gt;all&lt;/em&gt; events on the system, no matter &lt;em&gt;how&lt;/em&gt; far away.)  

We're going to add a control that will let you set your own radius soon.</description>
		<content:encoded><![CDATA[<p>Right now the range is fixed at 80 miles.  (That seems really big, but keep in mind that  before this change, Mosuki showed you <em>all</em> events on the system, no matter <em>how</em> far away.)  </p>
<p>We&#8217;re going to add a control that will let you set your own radius soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Local events on Mosuki by ryssa</title>
		<link>http://blog.mosuki.com/47/local-events-on-mosuki#comment-1248</link>
		<dc:creator>ryssa</dc:creator>
		<pubDate>Wed, 03 Oct 2007 17:09:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mosuki.com/47/local-events-on-mosuki#comment-1248</guid>
		<description>What's the range on the zip codes?  i.e. is there a way to set it to show me events that are within 50/100/200 miles of my area, or am I stuck with the defaults for now?
(I know there are many SF people who don't ever venture into the East Bay, and vice versa.)</description>
		<content:encoded><![CDATA[<p>What&#8217;s the range on the zip codes?  i.e. is there a way to set it to show me events that are within 50/100/200 miles of my area, or am I stuck with the defaults for now?<br />
(I know there are many SF people who don&#8217;t ever venture into the East Bay, and vice versa.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Add an &#8220;export to Mosuki&#8221; button to your website by bryan</title>
		<link>http://blog.mosuki.com/40/add-an-export-to-mosuki-button-to-your-website#comment-1003</link>
		<dc:creator>bryan</dc:creator>
		<pubDate>Fri, 08 Jun 2007 20:37:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mosuki.com/40/add-an-export-to-mosuki-button-to-your-website#comment-1003</guid>
		<description>Hey, 

I like this! it is one step closer to me being able to add things on the fly!

Can I use this system to add things from my calender program (outlook and iCal) to mosuki?

How about a small app or java app for my phone and computer!</description>
		<content:encoded><![CDATA[<p>Hey, </p>
<p>I like this! it is one step closer to me being able to add things on the fly!</p>
<p>Can I use this system to add things from my calender program (outlook and iCal) to mosuki?</p>
<p>How about a small app or java app for my phone and computer!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google calendar: sharing gone wild! by glyphobet</title>
		<link>http://blog.mosuki.com/34/google-calendar-sharing-gone-wild#comment-887</link>
		<dc:creator>glyphobet</dc:creator>
		<pubDate>Tue, 24 Apr 2007 04:48:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mosuki.com/34/google-calendar-sharing-gone-wild#comment-887</guid>
		<description>Yes, Google calendar has had "Public" and "Private" settings for events and calendars created from within Google calendar for a long time.  

Google calendar does not have any privacy controls for events imported via a URL, and most people do not realize this because of the way that the interface is structured.  You can decide whether other people can "find this public calendar via Google Calendar search." However, even events in imported calendars set to not be findable contain only public events: if you look at the calendar details, it clearly says "Anyone can: See all event details."  

We were confused enough about this interface to perform a test a while back, and we found that any &lt;strong&gt;event&lt;/strong&gt; in any imported calendar will show up in Google calendar search, regardless of whether the user chose to make the &lt;strong&gt;calendar&lt;/strong&gt; findable. 

I'm sure you know this, since your business is based on integrating with Google calendar. :) I'm explaining it for the benefit of other people who are following our blog.  Imagine how damaging it would be if a competitor searched for your company name and a range like "Jan 1 2005 through Jan 1 2008" and found a bunch of sensitive business meetings about secret business deals?  Or imagine if that happened to one of your users, and they decided to sue you or Google?

I strongly (although respectfully) disagree with your assertion that "lazy users must share the blame" for these kinds of privacy breaches.  Certainly in this extreme example, I would place the blame entirely on Google, since pretty much everyone we talk to, on this blog or in person, is under the mistaken impression that Google supports private calendar feeds. If everyone who uses an application is confused about it, you can't really blame "lazy users." 

And I disagree in a broader sense too. It is possible to write software that is secure, with clear, simple, easy to use privacy controls.  The vast majority of computer users don't even think about privacy (at least until their privacy is breached).  The only way to get people to use privacy controls is to make them easy to use.  This is one of the core features of Mosuki.</description>
		<content:encoded><![CDATA[<p>Yes, Google calendar has had &#8220;Public&#8221; and &#8220;Private&#8221; settings for events and calendars created from within Google calendar for a long time.  </p>
<p>Google calendar does not have any privacy controls for events imported via a URL, and most people do not realize this because of the way that the interface is structured.  You can decide whether other people can &#8220;find this public calendar via Google Calendar search.&#8221; However, even events in imported calendars set to not be findable contain only public events: if you look at the calendar details, it clearly says &#8220;Anyone can: See all event details.&#8221;  </p>
<p>We were confused enough about this interface to perform a test a while back, and we found that any <strong>event</strong> in any imported calendar will show up in Google calendar search, regardless of whether the user chose to make the <strong>calendar</strong> findable. </p>
<p>I&#8217;m sure you know this, since your business is based on integrating with Google calendar. <img src='http://blog.mosuki.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> I&#8217;m explaining it for the benefit of other people who are following our blog.  Imagine how damaging it would be if a competitor searched for your company name and a range like &#8220;Jan 1 2005 through Jan 1 2008&#8243; and found a bunch of sensitive business meetings about secret business deals?  Or imagine if that happened to one of your users, and they decided to sue you or Google?</p>
<p>I strongly (although respectfully) disagree with your assertion that &#8220;lazy users must share the blame&#8221; for these kinds of privacy breaches.  Certainly in this extreme example, I would place the blame entirely on Google, since pretty much everyone we talk to, on this blog or in person, is under the mistaken impression that Google supports private calendar feeds. If everyone who uses an application is confused about it, you can&#8217;t really blame &#8220;lazy users.&#8221; </p>
<p>And I disagree in a broader sense too. It is possible to write software that is secure, with clear, simple, easy to use privacy controls.  The vast majority of computer users don&#8217;t even think about privacy (at least until their privacy is breached).  The only way to get people to use privacy controls is to make them easy to use.  This is one of the core features of Mosuki.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google calendar: sharing gone wild! by Calgoo</title>
		<link>http://blog.mosuki.com/34/google-calendar-sharing-gone-wild#comment-883</link>
		<dc:creator>Calgoo</dc:creator>
		<pubDate>Mon, 23 Apr 2007 22:22:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mosuki.com/34/google-calendar-sharing-gone-wild#comment-883</guid>
		<description>Hi,

We at the Calgoo office use Google Calendar for business purposes.  Privacy settings on Google Calendar have always existed to our knowledge.  What the problem is is that users are not educated on how to use the program.  Google should make it more clear as to what the various privacy settings are and how to use them.  Also defaulting to private would make a lot of these headaches go away.  

Hard to blame just Google here though - lazy users must share this blame equally.

- Calgoo
www.calgoo.com</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>We at the Calgoo office use Google Calendar for business purposes.  Privacy settings on Google Calendar have always existed to our knowledge.  What the problem is is that users are not educated on how to use the program.  Google should make it more clear as to what the various privacy settings are and how to use them.  Also defaulting to private would make a lot of these headaches go away.  </p>
<p>Hard to blame just Google here though - lazy users must share this blame equally.</p>
<p>- Calgoo<br />
<a href="http://www.calgoo.com" rel="nofollow">http://www.calgoo.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Google calendar doesn&#8217;t work with Mosuki by Mosuki blog &#187; Google calendar: sharing gone wild!</title>
		<link>http://blog.mosuki.com/7/why-google-calendar-doesnt-work-with-mosuki#comment-881</link>
		<dc:creator>Mosuki blog &#187; Google calendar: sharing gone wild!</dc:creator>
		<pubDate>Mon, 23 Apr 2007 20:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mosuki.com/7/why-google-calendar-doesnt-work-with-mosuki#comment-881</guid>
		<description>[...] We posted eight months ago about Google calendar&#8217;s lack of respect for private data. Chris Pirillo has a found a clever demonstration of this: just search for &#8220;user password&#8221; in public events, and you&#8217;ll come up with a huge list of usernames and passwords of all sorts. [...]</description>
		<content:encoded><![CDATA[<p>[...] We posted eight months ago about Google calendar&#8217;s lack of respect for private data. Chris Pirillo has a found a clever demonstration of this: just search for &#8220;user password&#8221; in public events, and you&#8217;ll come up with a huge list of usernames and passwords of all sorts. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Subscription and export by Mosuki blog &#187; A favorable review</title>
		<link>http://blog.mosuki.com/4/subscription-and-export#comment-61</link>
		<dc:creator>Mosuki blog &#187; A favorable review</dc:creator>
		<pubDate>Tue, 31 Oct 2006 03:11:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mosuki.com/4/subscription-and-export#comment-61</guid>
		<description>[...] The author points out that you can download individual events as .ics files via the &#8220;Download Event&#8221; button, but doesn&#8217;t mention that you can also download your entire calendar in an .ics file, or subscribe to it in iCal and others, or import it into Outlook, from the calendar page. Maybe we need to make the subscription widget more obvious. [...]</description>
		<content:encoded><![CDATA[<p>[...] The author points out that you can download individual events as .ics files via the &#8220;Download Event&#8221; button, but doesn&#8217;t mention that you can also download your entire calendar in an .ics file, or subscribe to it in iCal and others, or import it into Outlook, from the calendar page. Maybe we need to make the subscription widget more obvious. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
