<?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: Avoiding Twitter Trouble &#8211; Legal and Regulatory Issues for Investor Relations	</title>
	<atom:link href="https://www.corporate-eye.com/main/avoiding-twitter-trouble-investor-relations/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.corporate-eye.com/main/avoiding-twitter-trouble-investor-relations/</link>
	<description>...compare, compete, excel</description>
	<lastBuildDate>Thu, 07 Jan 2021 14:11:15 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Maie		</title>
		<link>https://www.corporate-eye.com/main/avoiding-twitter-trouble-investor-relations/#comment-13677</link>

		<dc:creator><![CDATA[Maie]]></dc:creator>
		<pubDate>Wed, 12 Dec 2012 13:45:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.corporate-eye.com/blog/?p=30564#comment-13677</guid>

					<description><![CDATA[Hi Brian,

I&#039;d be interested to know your take on this latest offering by the SEC, although it is only the findings of a review, and once again not solid guidelines.

http://www.sec.gov/about/offices/ocie/riskalert-socialmedia.pdf]]></description>
			<content:encoded><![CDATA[<p>Hi Brian,</p>
<p>I&#8217;d be interested to know your take on this latest offering by the SEC, although it is only the findings of a review, and once again not solid guidelines.</p>
<p><a href="http://www.sec.gov/about/offices/ocie/riskalert-socialmedia.pdf" rel="nofollow ugc">http://www.sec.gov/about/offices/ocie/riskalert-socialmedia.pdf</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: ArticlePlaygrnd		</title>
		<link>https://www.corporate-eye.com/main/avoiding-twitter-trouble-investor-relations/#comment-10045</link>

		<dc:creator><![CDATA[ArticlePlaygrnd]]></dc:creator>
		<pubDate>Sat, 30 Jan 2010 14:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.corporate-eye.com/blog/?p=30564#comment-10045</guid>

					<description><![CDATA[That&#039;s why it&#039;s important that we carefully guide our words as we communitcae with others on Twitter, because some things can easily be taken the wrong way and out of context]]></description>
			<content:encoded><![CDATA[<p>That&#8217;s why it&#8217;s important that we carefully guide our words as we communitcae with others on Twitter, because some things can easily be taken the wrong way and out of context</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Brian		</title>
		<link>https://www.corporate-eye.com/main/avoiding-twitter-trouble-investor-relations/#comment-9756</link>

		<dc:creator><![CDATA[Brian]]></dc:creator>
		<pubDate>Sun, 06 Dec 2009 16:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.corporate-eye.com/blog/?p=30564#comment-9756</guid>

					<description><![CDATA[Darrell,
No skipping ahead! :)

This post was about the problems. The next one is about the solutions. &lt;a href=&quot;http://www.corporate-eye.com/main/blog/twitter-guide-investor-relations/&quot; rel=&quot;nofollow&quot;&gt;Twitter Strategy Guide for IR&lt;/a&gt;. The one after that, coming soon, is about just how to make good tweets, and one of the main points is to &quot;Always Tweet Links&quot; which is what you were suggesting.

Thanks for reading.

Brian]]></description>
			<content:encoded><![CDATA[<p>Darrell,<br />
No skipping ahead! :)</p>
<p>This post was about the problems. The next one is about the solutions. <a href="http://www.corporate-eye.com/main/blog/twitter-guide-investor-relations/" rel="nofollow">Twitter Strategy Guide for IR</a>. The one after that, coming soon, is about just how to make good tweets, and one of the main points is to &#8220;Always Tweet Links&#8221; which is what you were suggesting.</p>
<p>Thanks for reading.</p>
<p>Brian</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: uberVU - social comments		</title>
		<link>https://www.corporate-eye.com/main/avoiding-twitter-trouble-investor-relations/#comment-9605</link>

		<dc:creator><![CDATA[uberVU - social comments]]></dc:creator>
		<pubDate>Thu, 12 Nov 2009 16:55:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.corporate-eye.com/blog/?p=30564#comment-9605</guid>

					<description><![CDATA[&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by pkiss: What about integrating Twitter on co&#039;s site via a widget? RT @tweetmeme Avoid Twitter Trouble Investor Relations http://bit.ly/3v0rmG...]]></description>
			<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by pkiss: What about integrating Twitter on co&#8217;s site via a widget? RT @tweetmeme Avoid Twitter Trouble Investor Relations <a href="http://bit.ly/3v0rmG" rel="nofollow ugc">http://bit.ly/3v0rmG</a>&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Darrell Heaps		</title>
		<link>https://www.corporate-eye.com/main/avoiding-twitter-trouble-investor-relations/#comment-9599</link>

		<dc:creator><![CDATA[Darrell Heaps]]></dc:creator>
		<pubDate>Thu, 12 Nov 2009 02:53:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.corporate-eye.com/blog/?p=30564#comment-9599</guid>

					<description><![CDATA[Hi Brian, 

Nice post, however an easy way for the company to deal with this situation is to post the complete 414 character answer in their FAQ section of their IR website (or blog if they have one) and then simply link to it from Twitter.

The vast majority of tweets shared through Twitter include links to websites, the whole restriction of &quot;140 characters&quot; is not a restriction for companies if they focus on using their IR site effectively and linking back to it from Twitter. 

Cheers, 

Darrell]]></description>
			<content:encoded><![CDATA[<p>Hi Brian, </p>
<p>Nice post, however an easy way for the company to deal with this situation is to post the complete 414 character answer in their FAQ section of their IR website (or blog if they have one) and then simply link to it from Twitter.</p>
<p>The vast majority of tweets shared through Twitter include links to websites, the whole restriction of &#8220;140 characters&#8221; is not a restriction for companies if they focus on using their IR site effectively and linking back to it from Twitter. </p>
<p>Cheers, </p>
<p>Darrell</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
