<?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"
	>
<channel>
	<title>Comments on: Not happy with how the Twitter digests work</title>
	<atom:link href="http://stilgherrian.com/blogging/not_happy_twitter_digests/feed/" rel="self" type="application/rss+xml" />
	<link>http://stilgherrian.com/blogging/not_happy_twitter_digests/</link>
	<description>All publication is a political act. All communication is propaganda. All art is pornography. All business is personal. All hail Eris. Vive le poisson rouge sauvages!</description>
	<pubDate>Fri, 05 Sep 2008 06:27:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Stilgherrian &#183; Link digests: an experiment</title>
		<link>http://stilgherrian.com/blogging/not_happy_twitter_digests/#comment-11563</link>
		<dc:creator>Stilgherrian &#183; Link digests: an experiment</dc:creator>
		<pubDate>Thu, 13 Mar 2008 18:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://stilgherrian.com/blogging/not_happy_twitter_digests/#comment-11563</guid>
		<description>[...] the websites I find in del.icio.us and publishing a daily collection here. Just as with the daily Twitter updates, though, the list of random pieces changes the character of the site. And the experimental system [...]</description>
		<content:encoded><![CDATA[<p>[...] the websites I find in del.icio.us and publishing a daily collection here. Just as with the daily Twitter updates, though, the list of random pieces changes the character of the site. And the experimental system [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stilgherrian</title>
		<link>http://stilgherrian.com/blogging/not_happy_twitter_digests/#comment-11535</link>
		<dc:creator>Stilgherrian</dc:creator>
		<pubDate>Wed, 12 Mar 2008 05:48:48 +0000</pubDate>
		<guid isPermaLink="false">http://stilgherrian.com/blogging/not_happy_twitter_digests/#comment-11535</guid>
		<description>&lt;strong&gt;@jason:&lt;/strong&gt; That's the way to go, yes. I'd even be happy with a headline link only -- none of the Tweets themselves visible on the "main" pages.

I'm trying to think how I can bolt that together without having to do any coding of my own. (1) Completely separate blog tool to just hold the Tweet summaries, and post the headline here automatically. (2) Point the problem back to the Twitter Tools author and get him to add some options.</description>
		<content:encoded><![CDATA[<p><strong>@jason:</strong> That&#8217;s the way to go, yes. I&#8217;d even be happy with a headline link only &#8212; none of the Tweets themselves visible on the &#8220;main&#8221; pages.</p>
<p>I&#8217;m trying to think how I can bolt that together without having to do any coding of my own. (1) Completely separate blog tool to just hold the Tweet summaries, and post the headline here automatically. (2) Point the problem back to the Twitter Tools author and get him to add some options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason</title>
		<link>http://stilgherrian.com/blogging/not_happy_twitter_digests/#comment-11534</link>
		<dc:creator>jason</dc:creator>
		<pubDate>Wed, 12 Mar 2008 05:29:59 +0000</pubDate>
		<guid isPermaLink="false">http://stilgherrian.com/blogging/not_happy_twitter_digests/#comment-11534</guid>
		<description>Ah, sorry missed that.

Problem is, you are a very prolific twitterer. In fact, it's more like the neighbors rooster crowing for a couple of hours at day break.

Maybe you could make use of a standfirst, showing the first few twitters, and then link through to the full horror. Not sure if that could be automated easily.</description>
		<content:encoded><![CDATA[<p>Ah, sorry missed that.</p>
<p>Problem is, you are a very prolific twitterer. In fact, it&#8217;s more like the neighbors rooster crowing for a couple of hours at day break.</p>
<p>Maybe you could make use of a standfirst, showing the first few twitters, and then link through to the full horror. Not sure if that could be automated easily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stilgherrian</title>
		<link>http://stilgherrian.com/blogging/not_happy_twitter_digests/#comment-11529</link>
		<dc:creator>Stilgherrian</dc:creator>
		<pubDate>Wed, 12 Mar 2008 02:53:58 +0000</pubDate>
		<guid isPermaLink="false">http://stilgherrian.com/blogging/not_happy_twitter_digests/#comment-11529</guid>
		<description>&lt;strong&gt;@jason:&lt;/strong&gt; I already have that, updated every 15 minutes or something. What I'm after is the archiving which isn't at Twitter in case they disappear when the Web 2.0 bubble bursts.</description>
		<content:encoded><![CDATA[<p><strong>@jason:</strong> I already have that, updated every 15 minutes or something. What I&#8217;m after is the archiving which isn&#8217;t at Twitter in case they disappear when the Web 2.0 bubble bursts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason</title>
		<link>http://stilgherrian.com/blogging/not_happy_twitter_digests/#comment-11528</link>
		<dc:creator>jason</dc:creator>
		<pubDate>Wed, 12 Mar 2008 02:48:28 +0000</pubDate>
		<guid isPermaLink="false">http://stilgherrian.com/blogging/not_happy_twitter_digests/#comment-11528</guid>
		<description>Why not have a dynamic twitter feed in the LHC?  Posting them as a story seems a bit odd.</description>
		<content:encoded><![CDATA[<p>Why not have a dynamic twitter feed in the LHC?  Posting them as a story seems a bit odd.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
