<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Degutis Insights - Latest Comments in 3rd party apps must make up for Twitter&amp;#8217;s incompetence</title><link>http://frumpa.disqus.com/</link><description></description><language>en</language><lastBuildDate>Fri, 25 Jul 2008 01:29:43 -0000</lastBuildDate><item><title>Re: 3rd party apps must make up for Twitter&amp;#8217;s incompetence</title><link>http://www.degutis.com/blog/3rd-party-apps-twitters-incompetence/#comment-997364</link><description>Now I see your point with third-party apps making up for Twitter incompetence. Sure, backup of our data could be a great addition to the services we already use as Twitter clients and I also expect to see some other backup apps intended solely to back up the followers in the nearest few days. But the problem is that they won'tsolve the core problem of Twitter instability - even if you have a backup, you can still import it Twitter only while a better option would be to be able to export the data to other substitute services.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">profy</dc:creator><pubDate>Fri, 25 Jul 2008 01:29:43 -0000</pubDate></item><item><title>Re: 3rd party apps must make up for Twitter&amp;#8217;s incompetence</title><link>http://www.degutis.com/blog/3rd-party-apps-twitters-incompetence/#comment-993997</link><description>TweetDeck also keeps the list of followers in the same database, which is fully accessible offline. A number of people have been using it to recreate their following list before Twitter gets round to fixing it e.g. &lt;a href="http://twitter.com/erasrhed42/statuses/867368520" rel="nofollow"&gt;http://twitter.com/erasrhed42/statuses/867368520&lt;/a&gt; &lt;a href="http://twitter.com/abelara/statuses/867307568" rel="nofollow"&gt;http://twitter.com/abelara/statuses/867307568&lt;/a&gt; &lt;a href="http://twitter.com/KevinHazzard/statuses/867494783" rel="nofollow"&gt;http://twitter.com/KevinHazzard/statuses/867494783&lt;/a&gt;&lt;br&gt;&lt;br&gt;You're post makes a great point about how twitter app developers have to add more value than most just to deal with twitter outages and API inconsistencies. I do wonder how long this good will from developers can last.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">iaindodsworth</dc:creator><pubDate>Thu, 24 Jul 2008 18:03:42 -0000</pubDate></item><item><title>Re: 3rd party apps must make up for Twitter&amp;#8217;s incompetence</title><link>http://www.degutis.com/blog/3rd-party-apps-twitters-incompetence/#comment-992183</link><description>Sounds pretty trivial for a Cocoa programming to do this kind of thing, especially with &lt;a href="http://mattgemmell.com/2008/02/22/mgtwitterengine-twitter-from-cocoa" rel="nofollow"&gt;this Twitter class&lt;/a&gt; from a friend. I think I might actually be up to the challenge in the next few months, if I get any spare time.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sdegutis</dc:creator><pubDate>Thu, 24 Jul 2008 15:24:19 -0000</pubDate></item></channel></rss>