<?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"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Protecting Your Email Communication from Social Media</title> <atom:link href="http://churchcrunch.com/protecting-your-email-communication-from-social-media/feed/" rel="self" type="application/rss+xml" /><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/</link> <description>Exploring the Intersection of Web Technology and the Church</description> <lastBuildDate>Sat, 20 Mar 2010 18:51:05 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" /> <item><title>By: Stuart</title><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/comment-page-1/#comment-50514</link> <dc:creator>Stuart</dc:creator> <pubDate>Sun, 15 Nov 2009 04:51:10 +0000</pubDate> <guid
isPermaLink="false">http://churchcrunch.com/?p=6964#comment-50514</guid> <description>Can&#039;t speak for America but there&#039;s nothing legal about these disclaimers in the UK.
They&#039;re moral guides at best - but as Tyler said, if someone wants to broadcast the contents of an email then there is nothing stopping the morally ambivalent. </description> <content:encoded><![CDATA[<p>Can&#039;t speak for America but there&#039;s nothing legal about these disclaimers in the UK.</p><p>They&#039;re moral guides at best &#8211; but as Tyler said, if someone wants to broadcast the contents of an email then there is nothing stopping the morally ambivalent.</p> ]]></content:encoded> </item> <item><title>By: links for 2009-11-11 &#171; random thoughts and casual ruminations</title><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/comment-page-1/#comment-50359</link> <dc:creator>links for 2009-11-11 &#171; random thoughts and casual ruminations</dc:creator> <pubDate>Wed, 11 Nov 2009 12:08:19 +0000</pubDate> <guid
isPermaLink="false">http://churchcrunch.com/?p=6964#comment-50359</guid> <description>[...] Protecting Your Email Communication from Social Media &#8211; ChurchCrunch [...]</description> <content:encoded><![CDATA[<p>[...] Protecting Your Email Communication from Social Media &#8211; ChurchCrunch [...]</p> ]]></content:encoded> </item> <item><title>By: human3rror</title><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/comment-page-1/#comment-50354</link> <dc:creator>human3rror</dc:creator> <pubDate>Wed, 11 Nov 2009 11:19:07 +0000</pubDate> <guid
isPermaLink="false">http://churchcrunch.com/?p=6964#comment-50354</guid> <description>cool. </description> <content:encoded><![CDATA[<p>cool.</p> ]]></content:encoded> </item> <item><title>By: human3rror</title><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/comment-page-1/#comment-50353</link> <dc:creator>human3rror</dc:creator> <pubDate>Wed, 11 Nov 2009 11:19:06 +0000</pubDate> <guid
isPermaLink="false">http://churchcrunch.com/?p=6964#comment-50353</guid> <description>eh. i hesitate on calling this out... </description> <content:encoded><![CDATA[<p>eh. i hesitate on calling this out&#8230;</p> ]]></content:encoded> </item> <item><title>By: human3rror</title><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/comment-page-1/#comment-50352</link> <dc:creator>human3rror</dc:creator> <pubDate>Wed, 11 Nov 2009 11:18:05 +0000</pubDate> <guid
isPermaLink="false">http://churchcrunch.com/?p=6964#comment-50352</guid> <description>yeah, it&#039;s true, but it just adds another layer.&lt;br /&gt;&lt;br /&gt;it also provide some \&quot;legal\&quot; net of sorts I suppose.&lt;br /&gt;&lt;br /&gt;nothing&#039;s stopping anyone, that&#039;s for sure. but, it&#039;ll hurt all the same if it comes up. </description> <content:encoded><![CDATA[<p>yeah, it&#39;s true, but it just adds another layer.</p><p>it also provide some \&#8221;legal\&#8221; net of sorts I suppose.</p><p>nothing&#39;s stopping anyone, that&#39;s for sure. but, it&#39;ll hurt all the same if it comes up.</p> ]]></content:encoded> </item> <item><title>By: Tyler_Braun</title><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/comment-page-1/#comment-50349</link> <dc:creator>Tyler_Braun</dc:creator> <pubDate>Wed, 11 Nov 2009 07:29:11 +0000</pubDate> <guid
isPermaLink="false">http://churchcrunch.com/?p=6964#comment-50349</guid> <description>So how does this stop someone from using your words? I don&#039;t get it. It discourages them against it sure, but they can still do whatever they please. </description> <content:encoded><![CDATA[<p>So how does this stop someone from using your words? I don&#039;t get it. It discourages them against it sure, but they can still do whatever they please.</p> ]]></content:encoded> </item> <item><title>By: Daniel_Berman</title><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/comment-page-1/#comment-50342</link> <dc:creator>Daniel_Berman</dc:creator> <pubDate>Wed, 11 Nov 2009 05:33:58 +0000</pubDate> <guid
isPermaLink="false">http://churchcrunch.com/?p=6964#comment-50342</guid> <description>I can definitely understand the motivation behind such attempts as listed above, I guess the question comes down to the actual effectiveness in producing something that is legally binding....
Just because I receive such a notice in an email does not mean that I actually agree to not divulge such information, I wouldn&#039;t but for the sake of the argument. It runs along similar lines to the licenses from MS, that suggest that by opening the product you agree to the license even if you never read it or sign it....
I guess I am just left scratching my head on this one... </description> <content:encoded><![CDATA[<p>I can definitely understand the motivation behind such attempts as listed above, I guess the question comes down to the actual effectiveness in producing something that is legally binding&#8230;.</p><p>Just because I receive such a notice in an email does not mean that I actually agree to not divulge such information, I wouldn&#039;t but for the sake of the argument. It runs along similar lines to the licenses from MS, that suggest that by opening the product you agree to the license even if you never read it or sign it&#8230;.</p><p>I guess I am just left scratching my head on this one&#8230;</p> ]]></content:encoded> </item> <item><title>By: markalves</title><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/comment-page-1/#comment-50339</link> <dc:creator>markalves</dc:creator> <pubDate>Wed, 11 Nov 2009 03:52:56 +0000</pubDate> <guid
isPermaLink="false">http://churchcrunch.com/?p=6964#comment-50339</guid> <description>Interesting approach. I wonder, though, if some users of such a disclaimer would end up with a false sense of security. It&#039;s hard to declare all of your messages off the record by default when you&#039;re sharing them via an electronic record. Handling this on an as-needed basis would seem to be clearer than relying on fine print.
Also, what about situations where an email is being read through an employer&#039;s network? In those cases, the recipient has probably signed an agreement acknowledging the employer has rights to any such traffic. </description> <content:encoded><![CDATA[<p>Interesting approach. I wonder, though, if some users of such a disclaimer would end up with a false sense of security. It&#039;s hard to declare all of your messages off the record by default when you&#039;re sharing them via an electronic record. Handling this on an as-needed basis would seem to be clearer than relying on fine print.</p><p>Also, what about situations where an email is being read through an employer&#039;s network? In those cases, the recipient has probably signed an agreement acknowledging the employer has rights to any such traffic.</p> ]]></content:encoded> </item> <item><title>By: @purecommunity</title><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/comment-page-1/#comment-50335</link> <dc:creator>@purecommunity</dc:creator> <pubDate>Tue, 10 Nov 2009 20:51:29 +0000</pubDate> <guid
isPermaLink="false">http://churchcrunch.com/?p=6964#comment-50335</guid> <description>What are some of the recent happenings being referred to here? </description> <content:encoded><![CDATA[<p>What are some of the recent happenings being referred to here?</p> ]]></content:encoded> </item> <item><title>By: Name:Alex</title><link>http://churchcrunch.com/protecting-your-email-communication-from-social-media/comment-page-1/#comment-50334</link> <dc:creator>Name:Alex</dc:creator> <pubDate>Tue, 10 Nov 2009 20:47:10 +0000</pubDate> <guid
isPermaLink="false">http://churchcrunch.com/?p=6964#comment-50334</guid> <description>I work for a large church, our IT dept has setup the exchange server to automatically add a massive disclaimer to each email heading out of our network.Intrusive? Yes
Ugly? Yes
Effective? Highly.</description> <content:encoded><![CDATA[<p>I work for a large church, our IT dept has setup the exchange server to automatically add a massive disclaimer to each email heading out of our network.</p><p>Intrusive? Yes<br
/> Ugly? Yes<br
/> Effective? Highly.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: churchcrunch.com @ 2010-03-20 15:05:52 by W3 Total Cache -->