<?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"
	>

<channel>
	<title>yojibee &#187; Social</title>
	<atom:link href="http://www.yojibee.com/category/social/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yojibee.com</link>
	<description>the world according to a tech geek girl</description>
	<pubDate>Tue, 28 Oct 2008 16:26:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
	<language>en</language>
			<item>
		<title>Twitter and Summize</title>
		<link>http://www.yojibee.com/2008/06/26/twitter-and-summize/</link>
		<comments>http://www.yojibee.com/2008/06/26/twitter-and-summize/#comments</comments>
		<pubDate>Thu, 26 Jun 2008 09:02:15 +0000</pubDate>
		<dc:creator>yojibee</dc:creator>
		
		<category><![CDATA[Social]]></category>

		<category><![CDATA[Twitter]]></category>

		<category><![CDATA[Web2.0]]></category>

		<category><![CDATA[summize]]></category>

		<guid isPermaLink="false">http://www.yojibee.com/?p=398</guid>
		<description><![CDATA[I found this update on the Twitter Status blog this morning interesting:
&#8220;The replies tab remains disabled today as we rework some of the queries that were causing problems yesterday. This has also been reflected in the sidebar of the status blog for the web features.
One way you can see replies directed to you is to [...]]]></description>
			<content:encoded><![CDATA[<p>I found this update on the Twitter Status blog this morning interesting:</p>
<p>&#8220;The replies tab remains disabled today as we rework some of the queries that were causing problems yesterday. This has also been reflected in the sidebar of the status blog for the web features.<br />
One way you can see replies directed to you is to search on <a href="http://summize.com/">Summize</a>. You can search for “to:username” to see all updates directed at you.&#8221;</p>
<p>Twitter now encourages us to use third-party services, for functionalities they cannot deliver themselves anymore. </p>
<p>I know they have partnered with Summize before, for instance during Steve Job&#8217;s recent keynote (you can read about it <a href="http://www.techcrunch.com/2008/06/09/twitter-partners-with-summize-to-cover-apple-news/">here</a>), to reduce their database load.</p>
<p>But this time they are outsourcing a basic functionality of their own system, which makes me wonder what is left of what Twitter once was?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.yojibee.com/2008/06/26/twitter-and-summize/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Just a thought I cannot stop thinking about</title>
		<link>http://www.yojibee.com/2008/06/24/just-a-thought-i-cannot-stop-thinking-about/</link>
		<comments>http://www.yojibee.com/2008/06/24/just-a-thought-i-cannot-stop-thinking-about/#comments</comments>
		<pubDate>Tue, 24 Jun 2008 12:49:13 +0000</pubDate>
		<dc:creator>yojibee</dc:creator>
		
		<category><![CDATA[Social]]></category>

		<category><![CDATA[Twitter]]></category>

		<category><![CDATA[Web2.0]]></category>

		<category><![CDATA[api]]></category>

		<guid isPermaLink="false">http://www.yojibee.com/?p=396</guid>
		<description><![CDATA[It amazes me how busy I am wishing Twitter was back to normal again these days.
It just feels so awkward after so many months of using third party apps, that I had to revert to my browser to tweet again. I even had to go back to m.twitter.com on my iPhone.
By now, realizing that IM [...]]]></description>
			<content:encoded><![CDATA[<p>It amazes me how busy I am wishing Twitter was back to normal again these days.<br />
It just feels so awkward after so many months of using third party apps, that I had to revert to my browser to tweet again. I even had to go back to m.twitter.com on my iPhone.</p>
<p>By now, realizing that IM and Track will still be offline a while, all I wish for is an API that allows 70 req/hour again. I feel like half-a-person without the tweets trickling into Twitterrific/Growl.</p>
<p>Twitter have one of the most open APIs around, and I also think this was part of their recent headaches. (getting crushed by API calls)<br />
We all gave our Twitter credentials to any third-party app that came along and looked interesting. We had a zillion different Twitter clients, Twitter search, Twitter karma services and we wanted to try it all out.</p>
<p>A while ago I listened to the Gillmor Gang discussing Twitter once again.<br />
We all know Steve&#8217;s &#8220;obsession&#8221; with Track, so part of the conversation somehow got lost, and I haven&#8217;t been able to stop reflecting about this part ever since.</p>
<p>Chris Messina brought this up while discussing OAuth:</p>
<p>&#8221; So, you don’t actually have specific control to say, “I want to turn off access from Twitterific.&#8221;&#8230; You know, it’s like Flickr provides a great model of how you can turn on and off access from different services. This is just an example of one of the things that if we had it, I think Twitter would not only be providing greater value, but it would be demonstrating a level of user control over the use of this system that would actually be, I think, leading to greater resilience.&#8221;</p>
<p>I don&#8217;t know why this model haven&#8217;t been discussed.<br />
I can only speak for myself, but in light of the recent problems, I would happily turn off Twitter access to at all the different services and clients I have tried out in the last months. I don&#8217;t even know myself anymore how many apps and services receive my tweets.</p>
<p>Implementing a flickr-like model, where you can see which third-party applications you are using and remove the permission for these if necessary, would be fantastic.<br />
As a user it is a great way to control where your credentials go and it wouldn&#8217;t hurt Twitter&#8217;s API either.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.yojibee.com/2008/06/24/just-a-thought-i-cannot-stop-thinking-about/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
