<?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: Twitter and Identica Dilemma</title>
	<atom:link href="http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/feed" rel="self" type="application/rss+xml" />
	<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma</link>
	<description>Viewpoints on technology, society, and government</description>
	<lastBuildDate>Tue, 14 May 2013 02:23:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: pROCKrammer</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-3612</link>
		<dc:creator>pROCKrammer</dc:creator>
		<pubDate>Sun, 12 Apr 2009 14:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-3612</guid>
		<description><![CDATA[IMHO, Identi.ca is more suitable for Programmers and Advanced users ...]]></description>
		<content:encoded><![CDATA[<p>IMHO, Identi.ca is more suitable for Programmers and Advanced users &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan Prodromou</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-3370</link>
		<dc:creator>Evan Prodromou</dc:creator>
		<pubDate>Tue, 10 Mar 2009 08:52:56 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-3370</guid>
		<description><![CDATA[No, there isn&#039;t. Good idea, though!]]></description>
		<content:encoded><![CDATA[<p>No, there isn&#8217;t. Good idea, though!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Carmody</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-3369</link>
		<dc:creator>Sean Carmody</dc:creator>
		<pubDate>Tue, 10 Mar 2009 02:42:54 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-3369</guid>
		<description><![CDATA[@Evan: Is there anyway to do a bulk change of the Jabber status for existing subscriptions?]]></description>
		<content:encoded><![CDATA[<p>@Evan: Is there anyway to do a bulk change of the Jabber status for existing subscriptions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan Prodromou</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-3174</link>
		<dc:creator>Evan Prodromou</dc:creator>
		<pubDate>Tue, 10 Feb 2009 12:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-3174</guid>
		<description><![CDATA[You /can/ specify that you only want notices from certain people over any particular channel (IM, SMS) in Identi.ca! See your &quot;subscriptions&quot; page. Each subscription has a checkbox to show which channel you want to receive notices on for that person.]]></description>
		<content:encoded><![CDATA[<p>You /can/ specify that you only want notices from certain people over any particular channel (IM, SMS) in Identi.ca! See your &#8220;subscriptions&#8221; page. Each subscription has a checkbox to show which channel you want to receive notices on for that person.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Changelog</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-2471</link>
		<dc:creator>The Changelog</dc:creator>
		<pubDate>Sat, 13 Sep 2008 05:24:09 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-2471</guid>
		<description><![CDATA[I&#039;ve lately been thinking about Twitter. I wanted some way to quickly post tweets from the command line. But I also wanted to be able to receive them in a non-intrusive way on all my machines. And I wanted to work with Twitter and Identi.ca both. No]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve lately been thinking about Twitter. I wanted some way to quickly post tweets from the command line. But I also wanted to be able to receive them in a non-intrusive way on all my machines. And I wanted to work with Twitter and Identi.ca both. No</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Decklin Foster</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-2469</link>
		<dc:creator>Decklin Foster</dc:creator>
		<pubDate>Fri, 12 Sep 2008 05:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-2469</guid>
		<description><![CDATA[I use twerp (http://code.google.com/p/pytwerp) with a combination of cron, grep, and watch.

Except for the problem of synchronizing multiple machines, it sounds like doing twerp &#124; grep from something biff-like might be what you want. (I haven&#039;t done this yet, but I&#039;m considering it.) It just spits out plain text, so, whatever you have the patience to duct tape together, I guess.

I do all this from one machine that I am pretty much perpetually logged into. The last-check date of a timeline is just saved in a dotfile, so unless you did something about that, you&#039;d see the same updates on each machine. Not sure if you have a way around that.

(In the long term, I want to do something like Warbo said. But in the meantime patches to support the Laconica API would be very welcome.)]]></description>
		<content:encoded><![CDATA[<p>I use twerp (<a href="http://code.google.com/p/pytwerp" rel="nofollow">http://code.google.com/p/pytwerp</a>) with a combination of cron, grep, and watch.</p>
<p>Except for the problem of synchronizing multiple machines, it sounds like doing twerp | grep from something biff-like might be what you want. (I haven&#8217;t done this yet, but I&#8217;m considering it.) It just spits out plain text, so, whatever you have the patience to duct tape together, I guess.</p>
<p>I do all this from one machine that I am pretty much perpetually logged into. The last-check date of a timeline is just saved in a dotfile, so unless you did something about that, you&#8217;d see the same updates on each machine. Not sure if you have a way around that.</p>
<p>(In the long term, I want to do something like Warbo said. But in the meantime patches to support the Laconica API would be very welcome.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Penny Leach</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-2466</link>
		<dc:creator>Penny Leach</dc:creator>
		<pubDate>Tue, 09 Sep 2008 08:03:42 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-2466</guid>
		<description><![CDATA[I think you want track, it&#039;s documented in the official twitter command list:

http://help.twitter.com/index.php?pg=kb.page&amp;id=75

About jabber.. it used to work. I miss it.

You might try  http://www.floodgap.com/software/ttytter/  if you&#039;re not already aware of it.]]></description>
		<content:encoded><![CDATA[<p>I think you want track, it&#8217;s documented in the official twitter command list:</p>
<p><a href="http://help.twitter.com/index.php?pg=kb.page&#038;id=75" rel="nofollow">http://help.twitter.com/index.php?pg=kb.page&#038;id=75</a></p>
<p>About jabber.. it used to work. I miss it.</p>
<p>You might try  <a href="http://www.floodgap.com/software/ttytter/" rel="nofollow">http://www.floodgap.com/software/ttytter/</a>  if you&#8217;re not already aware of it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luca Bruno</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-2465</link>
		<dc:creator>Luca Bruno</dc:creator>
		<pubDate>Tue, 09 Sep 2008 07:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-2465</guid>
		<description><![CDATA[You might want to try http://ping.fm/ to update both at once.]]></description>
		<content:encoded><![CDATA[<p>You might want to try <a href="http://ping.fm/" rel="nofollow">http://ping.fm/</a> to update both at once.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Warbo</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-2464</link>
		<dc:creator>Warbo</dc:creator>
		<pubDate>Tue, 09 Sep 2008 05:51:09 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-2464</guid>
		<description><![CDATA[It should be entirely possible to subscribe each person to a different Jabber resource (although may require a patch). A resource is part of a Jabber ID, and necessary for logging on multiple times at once. For example, I have an account on jabber.org&#039;s server with the username warbo, ie. warbo@jabber.org. However, I have Empathy (my main client) logging in as warbo@jabber.org/laptop, with others like Kopete set up to log in as warbo@jabber.org/kopete etc. The resource with the highest priority receives messages sent to warbo@jabber.org whilst each resource receives any messages sent specifically to it.

Resources are completely arbitrary, you could tell Identica to send Dave&#039;s updates to you@yourserver.org/dave and Bob&#039;s updates to you@yourserver.org/bob. That way you can get constant updates from Bob by having a chat program logged in as you@yourserver.org/bob, and only receive updates from Dave every 2 hours by having a program log in as you@yourself.org/dave every 2 hours (could be done from cron). You can have as many resources logged in at the same time as you like (limited by which server you are using), although the user interface in many chat applications not designed for this could get cluttered.

Having your normal chat program logged in to your account via a high priority resource will prevent those identica listening programs from receiving your regular messages (those sent to simply you@yourserver.org)

I&#039;ve not used Identica myself, but I&#039;ve done quite a bit of programming based on Jabber. Hope that made sense :)]]></description>
		<content:encoded><![CDATA[<p>It should be entirely possible to subscribe each person to a different Jabber resource (although may require a patch). A resource is part of a Jabber ID, and necessary for logging on multiple times at once. For example, I have an account on jabber.org&#8217;s server with the username warbo, ie. <a href="mailto:warbo@jabber.org">warbo@jabber.org</a>. However, I have Empathy (my main client) logging in as <a href="mailto:warbo@jabber.org">warbo@jabber.org</a>/laptop, with others like Kopete set up to log in as <a href="mailto:warbo@jabber.org">warbo@jabber.org</a>/kopete etc. The resource with the highest priority receives messages sent to <a href="mailto:warbo@jabber.org">warbo@jabber.org</a> whilst each resource receives any messages sent specifically to it.</p>
<p>Resources are completely arbitrary, you could tell Identica to send Dave&#8217;s updates to <a href="mailto:you@yourserver.org">you@yourserver.org</a>/dave and Bob&#8217;s updates to <a href="mailto:you@yourserver.org">you@yourserver.org</a>/bob. That way you can get constant updates from Bob by having a chat program logged in as <a href="mailto:you@yourserver.org">you@yourserver.org</a>/bob, and only receive updates from Dave every 2 hours by having a program log in as <a href="mailto:you@yourself.org">you@yourself.org</a>/dave every 2 hours (could be done from cron). You can have as many resources logged in at the same time as you like (limited by which server you are using), although the user interface in many chat applications not designed for this could get cluttered.</p>
<p>Having your normal chat program logged in to your account via a high priority resource will prevent those identica listening programs from receiving your regular messages (those sent to simply <a href="mailto:you@yourserver.org">you@yourserver.org</a>)</p>
<p>I&#8217;ve not used Identica myself, but I&#8217;ve done quite a bit of programming based on Jabber. Hope that made sense :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-2463</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Tue, 09 Sep 2008 05:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-2463</guid>
		<description><![CDATA[On the search everyone&#039;s tweets front I can provide a little bit of light.  You can search tweets at http://search.twitter.com/

One cool point is that the search comes back with a News feed, like this one http://search.twitter.com/search?q=debian
So you can subscribe to the news feed and get the latest tweets about whatever you would like to search for.  

As for identi.ca&#039;s all or nothing IM updates.  Man, do I hear you.  Some people you really WANT to hear from.  Others... well... just keeping up with them occasionally would be fine.  Being able to get a instant updates from a few people (but not everyone) would be really nice!]]></description>
		<content:encoded><![CDATA[<p>On the search everyone&#8217;s tweets front I can provide a little bit of light.  You can search tweets at <a href="http://search.twitter.com/" rel="nofollow">http://search.twitter.com/</a></p>
<p>One cool point is that the search comes back with a News feed, like this one <a href="http://search.twitter.com/search?q=debian" rel="nofollow">http://search.twitter.com/search?q=debian</a><br />
So you can subscribe to the news feed and get the latest tweets about whatever you would like to search for.  </p>
<p>As for identi.ca&#8217;s all or nothing IM updates.  Man, do I hear you.  Some people you really WANT to hear from.  Others&#8230; well&#8230; just keeping up with them occasionally would be fine.  Being able to get a instant updates from a few people (but not everyone) would be really nice!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: foo</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-2462</link>
		<dc:creator>foo</dc:creator>
		<pubDate>Tue, 09 Sep 2008 04:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-2462</guid>
		<description><![CDATA[I use IRC instead.

Seriously though, identica is based on free software, I&#039;m sure they would be happy to accept a patch to laconica for this.]]></description>
		<content:encoded><![CDATA[<p>I use IRC instead.</p>
<p>Seriously though, identica is based on free software, I&#8217;m sure they would be happy to accept a patch to laconica for this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen in Wichita</title>
		<link>http://changelog.complete.org/archives/750-twitter-and-identica-dilemma/comment-page-1#comment-2461</link>
		<dc:creator>Karen in Wichita</dc:creator>
		<pubDate>Tue, 09 Sep 2008 02:41:07 +0000</pubDate>
		<guid isPermaLink="false">http://changelog2.complete.org/archives/750-twitter-and-identica-dilemma.html#comment-2461</guid>
		<description><![CDATA[Not sure if it&#039;s a GReader issue or a Twitter one, but I subscribe to a few Twitter RSS feeds and they go several days between updates... four to seven, so far.

Though, given Twitters failwhale record, I&#039;m going to bet the problem is Twitter.]]></description>
		<content:encoded><![CDATA[<p>Not sure if it&#8217;s a GReader issue or a Twitter one, but I subscribe to a few Twitter RSS feeds and they go several days between updates&#8230; four to seven, so far.</p>
<p>Though, given Twitters failwhale record, I&#8217;m going to bet the problem is Twitter.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
