<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>somecanuckchick dot com &#187; twitter</title>
	<atom:link href="http://www.somecanuckchick.com/tag/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.somecanuckchick.com</link>
	<description>A Mari Usque Ad Mare...</description>
	<lastBuildDate>Mon, 15 Mar 2010 21:29:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Twitter continues to defend itself against a DoS attack</title>
		<link>http://www.somecanuckchick.com/twitter-continues-to-defend-itself-against-a-dos-attack/</link>
		<comments>http://www.somecanuckchick.com/twitter-continues-to-defend-itself-against-a-dos-attack/#comments</comments>
		<pubDate>Thu, 06 Aug 2009 16:20:56 +0000</pubDate>
		<dc:creator>scc</dc:creator>
				<category><![CDATA[etc]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[#failwhale]]></category>
		<category><![CDATA[#twitterfail]]></category>
		<category><![CDATA[fyi]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.somecanuckchick.com/?p=295</guid>
		<description><![CDATA[2 hours ago, Twitter reported that its web site was down&#8230; although, Twitter really was not sure why&#8230; 
According to Twitter&#8217;s status page, Twitter (now) says that it is/was under a denial of service attack (Wikipedia entry for Denial of Service Attack). 
In a statement to CNN, Twitter co-founder Biz Stone (Wikipedia entry for Biz [...]]]></description>
			<content:encoded><![CDATA[<p>2 hours ago, Twitter reported that <a href="http://status.twitter.com/post/157160617/site-is-down">its web site was down</a>&#8230; although, Twitter <a href="http://mashable.com/2009/08/06/twitter-down/">really was not sure why</a>&#8230; </p>
<p>According to Twitter&#8217;s <a href="http://status.twitter.com/">status page</a>, Twitter (now) says <a href="http://status.twitter.com/post/157191978/ongoing-denial-of-service-attack">that it is/was under a denial of service attack</a> (Wikipedia entry for <a href="http://en.wikipedia.org/wiki/Denial-of-service_attack">Denial of Service Attack</a>). </p>
<p>In a <a href="http://scitech.blogs.cnn.com/2009/08/06/statement-from-twitter-on-denial-of-service-attack/">statement to CNN</a>, Twitter co-founder <a href="http://www.bizstone.com/">Biz Stone</a> (Wikipedia entry for <a href="http://en.wikipedia.org/wiki/Biz_Stone">Biz Stone</a>) said:</p>
<p><em>&#8220;There&#8217;s no indication that this attack is related to any previous activities. We are currently the target of a denial of service attack. Attacks such as this are malicious efforts orchestrated to disrupt and make unavailable services such as online banks, credit card payment gateways, and in this case, Twitter for intended customers or users. We are defending against this attack now and will continue to update our status blog as we defend and later investigate.&#8221;</em></p>
<p>Twitter now claims that the web site is now back up&#8230; however, <a href="mailto:scc@somecanuckchick.com?subject=www">somecanuckchick</a> (still) cannot access Twitter, via the web site, TwitterFox, TwitterTools, etc.</p>
<p>In the meantime, <a href="http://www.techcrunch.com/2009/05/08/twitter-is-down-15-alternative-things-to-do/">here is a list of alternative things to do</a>.</p>
<p>Update, from <a href="http://status.twitter.com/post/157191978/ongoing-denial-of-service-attack">Twitter&#8217;s post regarding its recovery from the DoS attack</a>:</p>
<p><em>&#8220;As we recover, users will experience some longer load times and slowness. This includes timeouts to API clients. We’re working to get back to 100% as quickly as we can.&#8221;</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.somecanuckchick.com/twitter-continues-to-defend-itself-against-a-dos-attack/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twittequette, Twitterprocity, and #followfail</title>
		<link>http://www.somecanuckchick.com/twittequette-twitterprocity-and-followfail/</link>
		<comments>http://www.somecanuckchick.com/twittequette-twitterprocity-and-followfail/#comments</comments>
		<pubDate>Tue, 14 Jul 2009 02:25:33 +0000</pubDate>
		<dc:creator>somecanuckchick</dc:creator>
				<category><![CDATA[www]]></category>
		<category><![CDATA[#followfail]]></category>
		<category><![CDATA[tweeple]]></category>
		<category><![CDATA[twinterest]]></category>
		<category><![CDATA[twittequette]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[twitterprocity]]></category>
		<category><![CDATA[twitterverse]]></category>

		<guid isPermaLink="false">http://www.somecanuckchick.com/?p=284</guid>
		<description><![CDATA[I have noted an increase in email over the last month which address my twittequette, with respect to my twitterprocity — or lack thereof.  
I have also noted an increase in email over the last month, with respect to my cessation of twinterest, reflected in the removal of certain kinds of tweeple from my [...]]]></description>
			<content:encoded><![CDATA[<p>I have noted an increase in email over the last month which address my <em>twittequette</em>, with respect to my <em>twitterprocity</em> — or lack thereof.  </p>
<p>I have also noted an increase in email over the last month, with respect to my cessation of <em>twinterest</em>, reflected in the removal of certain kinds of <em>tweeple</em> from my Twitter stream. </p>
<p>Without further ado, here are the top <strong>5</strong> reasons I will (likely) not follow you, or stop following you altogether on Twitter.</p>
<ol>
<li>You have no Twitter avatar — When you sign up for Twitter, you are encouraged to upload an image that will represent you in the <em>twitterverse</em>.  With it, your Twitter profile appears more personable, identifies you in your followers&#8217; Twitter stream, and helps you to relate others.</li>
<li>You have no Twitter profile — Again, when you sign up for Twitter, you are encouraged to fill out details about yourself, specifically your location, link to your web site, and a little blurb about yourself.  This helps others to ascertain how interacting with you could add to their overall Twitter experience.</li>
<li>You have less than <strong>25</strong> followers — And you are following hundreds upon hundreds or thousands upon thousands of Twitter users.  In my opinion, Twitter is about quality, not quantity.</li>
<li>You have never updated your Twitter status — Or, you rarely update your Twitter status, or you have less than <strong>25</strong> Twitter status updates, or you update your Twitter status every <strong>5</strong> minutes.</li>
<li>Any and/or all of your Twitter activity has been, is now, and will continue to be about marketing a product and/or service to the <em>twitterverse</em> — A product and/or service which I will never ever want, much less need.</li>
</ol>
<p>Basically, a combination of any and/or all of the above could/would/should result in a lack of <em>twitterprocity</em> on my part, or a <strong>#followfail</strong>.  However, neither of these should reflect negatively on my <em>twittequette</em>.</p>
<p>Feel free to email <a href="mailto:scc@somecanuckchick.com?subject=www">somecanuckchick</a> regarding <em>twittequette</em>, <em>twitterprocity</em>, etc.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.somecanuckchick.com/twittequette-twitterprocity-and-followfail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twitter Giveth Back&#8230; Kinda.</title>
		<link>http://www.somecanuckchick.com/twitter-giveth-back-kinda/</link>
		<comments>http://www.somecanuckchick.com/twitter-giveth-back-kinda/#comments</comments>
		<pubDate>Wed, 13 May 2009 22:35:03 +0000</pubDate>
		<dc:creator>scc</dc:creator>
				<category><![CDATA[PR]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[www]]></category>
		<category><![CDATA[#fixreplies]]></category>
		<category><![CDATA[#twitterfail]]></category>
		<category><![CDATA[@replies]]></category>
		<category><![CDATA[twitosphere]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[twitterati]]></category>

		<guid isPermaLink="false">http://www.somecanuckchick.com/?p=248</guid>
		<description><![CDATA[Twitter Giveth &#038; Twitter Taketh Away&#8230; 
Now, Twitter Giveth Back&#8230; Kinda.
Twitter claims to have learned a lot between yesterday and this afternoon.
Twitter now has a band aid solution in place to #fixreplies.  
As of today, updates beginning with @username—that are not explicitly created by clicking on the reply icon—will be seen by everyone following [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.somecanuckchick.com/twitter-giveth-and-twitter-taketh-away/">Twitter Giveth &#038; Twitter Taketh Away</a>&#8230; </p>
<p>Now, Twitter Giveth Back&#8230; Kinda.</p>
<p>Twitter <a href="http://blog.twitter.com/2009/05/we-learned-lot.html">claims to have learned a lot</a> between <a href="http://blog.twitter.com/2009/05/small-settings-update.html">yesterday</a> and <a href="http://blog.twitter.com/2009/05/whoa-feedback.html">this afternoon</a>.</p>
<p>Twitter now has a band aid solution in place to #fixreplies.  </p>
<p>As of today, <em>updates beginning with @username—that are not explicitly created by clicking on the reply icon—will be seen by everyone following that Twitter account</em>.  </p>
<p>Twitter also says that <em>a new feature—which will give folks more control over what they see from the accounts they follow—is being designed</em>.  </p>
<p>In short, Twitter will not be reverting to the previous @replies system.  </p>
<p>Twitter acknowledges that while Twitter users loved the feature, <em>it was confusing and caused a sense of inconsistency</em>.  </p>
<p>What do you think of the band aid solution?  Do you think Twitter can do better than the previous @replies system?</p>
<p>Let <a href="mailto:scc@somecanuckchick.com?subject=www">somecanuckchick</a> know!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.somecanuckchick.com/twitter-giveth-back-kinda/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
