<?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>Be the signal &#187; Twitter</title>
	<atom:link href="http://bethesignal.org/blog/tag/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://bethesignal.org</link>
	<description>where we&#039;re going, we don&#039;t need roads...</description>
	<lastBuildDate>Thu, 26 Jan 2012 05:52:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<atom:link rel='hub' href='http://bethesignal.org/?pushpress=hub'/>
		<item>
		<title>Packet and Denby</title>
		<link>http://bethesignal.org/blog/2010/08/15/packet-and-denby/</link>
		<comments>http://bethesignal.org/blog/2010/08/15/packet-and-denby/#comments</comments>
		<pubDate>Sun, 15 Aug 2010 13:53:33 +0000</pubDate>
		<dc:creator>Jeff Waugh</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[denby]]></category>
		<category><![CDATA[html5]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[nodejs]]></category>
		<category><![CDATA[packet]]></category>
		<category><![CDATA[scooter]]></category>
		<category><![CDATA[socket.io]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[websockets]]></category>

		<guid isPermaLink="false">http://bethesignal.org/?p=1741</guid>
		<description><![CDATA[This is Packet. This is Denby. I mention in the video that it&#8217;ll end up being &#8220;like TweetDeck&#8221;. I breezed past that a tad too quickly &#8212; it&#8217;s definitely not going to be an HTML5 clone of TweetDeck! (Turns out &#8230; <a href="http://bethesignal.org/blog/2010/08/15/packet-and-denby/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<h2>This is Packet.</h2>
<p><img style=' display: block; margin-right: auto; margin-left: auto;'  class="aligncenter size-large wp-image-1755" title="Packet's Speedo vs. Speed" src="http://bethesignal.org/wp-content/uploads/2010/08/speedo-220-bike-50-640x478.jpg" alt="" width="640" height="478" /></p>
<h2>This is <a title="Denby" href="http://www.hellodenby.com/">Denby</a>.</h2>
<p><video tabindex="0" type="video/ogg;codecs='theora,vorbis'" src="http://bethesignal.org/wp-content/uploads/2010/08/denby-01-prototype.ogv" poster="http://bethesignal.org/wp-content/uploads/2010/08/denby-01-prototype-640x284.png" preload="none" controls="true" height="284" width="640"><a href="http://bethesignal.org/wp-content/uploads/2010/08/denby-01-prototype.ogv"><img style=' display: block; margin-right: auto; margin-left: auto;'  class="aligncenter size-large wp-image-1759" title="Denby Prototype Video (Ogg/Theora)" src="http://bethesignal.org/wp-content/uploads/2010/08/denby-01-prototype-640x284.png" alt="" width="640" height="284" /></a></video></p>
<p>I mention in the video that it&#8217;ll end up being &#8220;like TweetDeck&#8221;. I breezed past that a tad too quickly &#8212; it&#8217;s definitely not going to be an HTML5 clone of TweetDeck! (Turns out they&#8217;re working on one of those already.)</p>
<p>Instead, it will take inspiration from the multi-column approach, but hopefully improve the user experience on a number of levels:</p>
<ul>
<li>It&#8217;ll be 100% Free Software / Open Source&#8230; and one hopes, peer produced.</li>
<li>JavaScript on the server, JavaScript on the client, with liberal doses of &#8220;HTML5&#8243; (the platform your platform could be), whatever that means to you.</li>
<li>No Adobe AIR, and thus, no vicious memory and CPU abuse! Seriously: <del title="Firefox? What was I thinking when I wrote this?">Firefox</del> TweetDeck is wasting more CPU time sitting &#8220;idle&#8221; than Chromium and node.js are using to run Denby. Oh, and node.js is 12MB resident.</li>
<li>It can work a bit like a desktop app&#8230; use the &#8220;web page as application&#8221; tool your browser provides. Firefox has Prism, Chromium has&#8230; a menu item. <img width='16' height='16' src='http://bethesignal.org/wp-content/plugins/tango-smilies/tango/face-wink.png' alt=';-)' class='wp-smiley' />  Denby will support things like desktop notifications, audio bleeps, drag-n-drop (for media uploads), inline display of media, etc.</li>
<li>Run local or hosted. Once I&#8217;m happy with the user experience, I&#8217;ll start thinking about cool things the server could do while you&#8217;re not connected to it! For now, it only maintains the connection to Twitter while a client is connected.</li>
<li>I want to build delicious multiple account support, without complicating the single account experience. It&#8217;ll merge streams, detect the context you&#8217;re acting upon (click reply and you&#8217;ll be replying from the appropriate account), etc.</li>
</ul>
<p>Please comment if you have any thoughts or suggestions&#8230; crimes committed by other Twitter clients, ideas for lovely web/desktop integration, and so on. Thanks! <img width='16' height='16' src='http://bethesignal.org/wp-content/plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' /> </p>
<p><a title="Denby" href="http://www.hellodenby.com/">HELLO DENBY</a>.</p>
<p style="text-align: center;">* * *</p>
<p>Note that I&#8217;ve already had questions about StatusNet and identi.ca support. Thus far, they don&#8217;t have user streams, which was one of the main reasons behind building Denby. That said, it is entirely possible for the Denby server to poll the REST API (given that it already talks to Twitter&#8217;s) and send the results down the WebSockets tube&#8230; so, we&#8217;ll see.</p>
<p>Hmm. Perhaps this is the best way to build a user streams API for StatusNet anyway? The web app could send JSON messages to node.js, which could relay them to the intended users&#8230; via multiple protocols! Long-running HTTP, WebSockets, whatever. If anyone is inspired to do this, StatusNet could have a bi-directional WebSockets API before Twitter does!</p>
<p style="text-align: center;">* * *</p>
<p><strong>Update:</strong> I made another quick video, showing a few improvements (including update bleeps &#8212; no chicken noises as yet), Denby in Firefox&#8217;s Prism environment, and sharing some thoughts about the web as a development platform. Enjoy!</p>
<p><video tabindex="0" type="video/ogg;codecs='theora,vorbis'" src="http://bethesignal.org/wp-content/uploads/2010/08/denby-02-prototype.ogv" poster="http://bethesignal.org/wp-content/uploads/2010/08/denby-02-prototype-640x330.png" preload="none" controls="true" height="330" width="640"><a href="http://bethesignal.org/wp-content/uploads/2010/08/denby-02-prototype.ogv"><img style=' display: block; margin-right: auto; margin-left: auto;'  class="aligncenter size-large wp-image-1771" title="Denby Prototype Video 2 (Ogg/Theora)" src="http://bethesignal.org/wp-content/uploads/2010/08/denby-02-prototype-640x330.png" alt="" width="640" height="330" /></a></video></p>
]]></content:encoded>
			<wfw:commentRss>http://bethesignal.org/blog/2010/08/15/packet-and-denby/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
<enclosure url="http://bethesignal.org/wp-content/uploads/2010/08/denby-01-prototype.ogv" length="12808118" type="video/ogg" />
<enclosure url="http://bethesignal.org/wp-content/uploads/2010/08/denby-02-prototype.ogv" length="22335152" type="video/ogg" />
		</item>
		<item>
		<title>No Twitter Sex For You</title>
		<link>http://bethesignal.org/blog/2008/07/31/no-twitter-sex-for-you/</link>
		<comments>http://bethesignal.org/blog/2008/07/31/no-twitter-sex-for-you/#comments</comments>
		<pubDate>Wed, 30 Jul 2008 18:41:47 +0000</pubDate>
		<dc:creator>Jeff Waugh</dc:creator>
				<category><![CDATA[Asides]]></category>
		<category><![CDATA[alex graveley]]></category>
		<category><![CDATA[chipx86]]></category>
		<category><![CDATA[christian hammond]]></category>
		<category><![CDATA[orph]]></category>
		<category><![CDATA[sex]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://bethesignal.org/?p=1172</guid>
		<description><![CDATA[&#8220;No Twitter sex for you&#8221; by ChipX86.]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><img class="size-full wp-image-1173 alignnone" title="No Twitter sex for you" src="http://bethesignal.org/wp-content/uploads/2008/07/notwittersex.png" alt="&quot;No Twitter sex for you&quot; by ChipX86" width="500" height="320" /></p>
<p style="text-align: center;">&#8220;No Twitter sex for you&#8221; by ChipX86. <img width='16' height='16' src='http://bethesignal.org/wp-content/plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://bethesignal.org/blog/2008/07/31/no-twitter-sex-for-you/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Projects that make my WordPress rock!</title>
		<link>http://bethesignal.org/blog/2008/07/26/projects-that-make-my-wordpress-rock/</link>
		<comments>http://bethesignal.org/blog/2008/07/26/projects-that-make-my-wordpress-rock/#comments</comments>
		<pubDate>Sat, 26 Jul 2008 05:53:48 +0000</pubDate>
		<dc:creator>Jeff Waugh</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[akismet]]></category>
		<category><![CDATA[bad behavior]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[opensearch]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[sandbox]]></category>
		<category><![CDATA[tango]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress MU]]></category>
		<category><![CDATA[WPMU]]></category>

		<guid isPermaLink="false">http://bethesignal.org/?p=1134</guid>
		<description><![CDATA[Here are some of the projects that I enjoy using with WordPress&#8230; Perhaps you&#8217;ll find them as useful as I have. WordPress and WordPress MU (multi-user) It&#8217;s hard to make recommendations related to WordPress without mentioning the project itself, and &#8230; <a href="http://bethesignal.org/blog/2008/07/26/projects-that-make-my-wordpress-rock/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Here are some of the projects that I enjoy using with WordPress&#8230; Perhaps you&#8217;ll find them as useful as I have.</p>
<ul>
<li>
<p><strong><a href="http://wordpress.org/">WordPress</a> and <a href="http://mu.wordpress.org/">WordPress <span class="caps">MU</span></a> (multi-user)</strong></p>
<p>It&#8217;s hard to make recommendations related to WordPress without mentioning the project itself, and its twisted sister, WordPress MU. Both are improving in leaps and bounds, and it&#8217;s a pleasure finding all the cool new things as I track their development trunks. WordPress 2.6 is the latest major release, with lots of cool new goodies&#8230; <a title="Holy Shmoly!" href="http://ocaoimh.ie/">Donncha</a> is rapidly catching up to those changes with WordPress MU. I wrote nice things about them on my <a href="http://bethesignal.org/blog/2008/01/14/projects-that-make-gnome-rock/">Projects that make GNOME rock!</a> post, too.</p>
</li>
<li>
<p><a href="http://www.plaintxt.org/themes/sandbox/"><strong>Sandbox</strong></a></p>
<p>I am a minimalist at heart, but with a fondness for cleverly expressive minimalism, so the Sandbox theme blows my mind. If you just look at the theme on the surface, it seems like a very boring, no-frills blob of unstyled HTML. But the genius lays waiting beneath the surface, in the highly evolved markup. Cunningly generated classes deliver extraordinary flexibility to a designer working with CSS. Just look at the body and div.post tags to get a good idea of what you can do. <a href="http://bethesignal.org/">Be the signal</a> is 100% Sandbox + custom CSS, with no added ingredients&#8230; and it changes colour every hour! <img width='16' height='16' src='http://bethesignal.org/wp-content/plugins/tango-smilies/tango/face-wink.png' alt=';-)' class='wp-smiley' /> </p>
</li>
<li>
<p><strong><a href="http://akismet.com/">Akismet</a> &amp; <a href="http://www.bad-behavior.ioerror.us/">Bad Behavior</a></strong></p>
<p>The one-two punch in my anti-blog-spam regime. Bad Behavior protects against abusive hosts and patterns of use, while Akismet does content filtering. As such, with an MTA analogy, they&#8217;re like a great combo of solid Postfix policy as front-line defense, plus DSPAM content filtering. Like my mailservers, I might not run both in every situation, but it&#8217;s great that they&#8217;re both available to protect the innocent. <img width='16' height='16' src='http://bethesignal.org/wp-content/plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' /> </p>
</li>
<li>
<p><a href="http://alexking.org/projects/wordpress"><strong>Twitter Tools</strong></a></p>
<p>Keeps my tweeps up to date with my blog, and lets my blog readers (bleeps?) know that I use Twitter and what I&#8217;m up to. I don&#8217;t use the daily blog archive feature, but lots of people enjoy that&#8230; despite it being one of the latest controversial content issues on Planets. I really ought to add <a href="http://identi.ca/">identi.ca</a> (or most likely &#8220;generic Twitter-style API&#8221;) support and see if Alex accepts the patch&#8230;</p>
</li>
<li>
<p><a href="http://wordpress.org/extend/plugins/openid"><strong>OpenID</strong></a></p>
<p>It&#8217;s great that companies and sites like Sun, AOL and MySpace are becoming OpenID providers, but the web really needs more consumers. So pretty much every WordPress blog I set up has Will Norris&#8217; WP-OpenID plugin installed. A while back I hacked it up to work with WordPress MU (always on, in mu-plugins), which was great for <a href="http://blogs.gnome.org/">GNOME Blogs</a>. I need to update that to the latest versions and see if Will might accept a nicer patch than the last one. <img width='16' height='16' src='http://bethesignal.org/wp-content/plugins/tango-smilies/tango/face-wink.png' alt=';-)' class='wp-smiley' /> </p>
</li>
<li>
<p><a href="http://wordpress.org/extend/plugins/wp-typogrify/"><strong>Typogrify</strong></a></p>
<p>As a card-carrying Font Fascist, it delights me that so many folks are working hard to improve typography on the web. I know that sounds a bit like &#8220;folks are working hard to improve oxygen on the moon&#8221;, but we&#8217;ll get there. <img width='16' height='16' src='http://bethesignal.org/wp-content/plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' />  Typogrify filters your posts to provide some cute ways of draining your own swamp, such as adding helpful markup to improve styleability of things like allcaps words, initial quotes, etc.</p>
</li>
<li>
<p><strong>My own cheesy plugins</strong></p>
<p>I&#8217;ve only managed to upload a few of my custom plugins to the WordPress Extend repository (which is a fantastic way to manage plugins for a widely-used platform, by the way), and thus far they&#8217;re kinda simple and cheesy.</p>
<ul>
<li><strong><a href="http://wordpress.org/extend/plugins/at-reply/">@reply</a></strong> automagically adds Twitter-style replying to your comments.</li>
<li><strong><a href="http://wordpress.org/extend/plugins/bug-links/">Bug Links</a></strong> adds stylish links to common FOSS bug tracking systems &#8212; this was mainly written for <a href="http://blogs.gnome.org/">GNOME Blogs</a>, so I&#8217;m particularly happy that Thomas uses it regularly for his very cool <a href="http://blogs.gnome.org/metacity/">metacity blog</a>.</li>
<li><strong><a href="http://wordpress.org/extend/plugins/opensearch/">OpenSearch</a><span title="Might not be available yet... check back soon!">*</span></strong> adds OpenSearch discovery to your WordPress site, so users can add your site to their search dropdown (in, say, Firefox). I need to improve it further to support the whole OpenSearch specification.</li>
<li><strong><span title="Might not be available yet... check back soon!"><a href="http://wordpress.org/extend/plugins/tango-smilies/">Tango Smilies</a></span></strong> makes your emoticons not look like arse!</li>
</ul>
</li>
</ul>
<p>Thanks, of course, to all of the developers and contributors to these projects. <img width='16' height='16' src='http://bethesignal.org/wp-content/plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://bethesignal.org/blog/2008/07/26/projects-that-make-my-wordpress-rock/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>inbox zero status: ZERO</title>
		<link>http://bethesignal.org/blog/2008/07/23/inbox-zero-status-zero/</link>
		<comments>http://bethesignal.org/blog/2008/07/23/inbox-zero-status-zero/#comments</comments>
		<pubDate>Tue, 22 Jul 2008 21:26:25 +0000</pubDate>
		<dc:creator>Jeff Waugh</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[identi.ca]]></category>
		<category><![CDATA[inbox zero]]></category>
		<category><![CDATA[laconi.ca]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[wget]]></category>

		<guid isPermaLink="false">http://bethesignal.org/?p=1097</guid>
		<description><![CDATA[After declaring inbox bankruptcy, changing the way I collect and manage my email, and tweeting a few times about my attempt to embrace the zen of Inbox Zero, I decided to automate the process, removing any potential editorialising between email &#8230; <a href="http://bethesignal.org/blog/2008/07/23/inbox-zero-status-zero/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>After declaring inbox bankruptcy, changing the way I collect and manage my email, and tweeting a few times about my attempt to embrace the zen of Inbox Zero, I decided to automate the process, removing any potential editorialising between email client and <a href="http://twitter.com/jdub/statuses/865495855">reporting</a> of the project status. <img width='16' height='16' src='http://bethesignal.org/wp-content/plugins/tango-smilies/tango/face-wink.png' alt=';-)' class='wp-smiley' />  I&#8217;ve set it up to post at 22:00 every night.</p>
<p>Here&#8217;s the script if anyone else wants to play (it also demonstrates how to post to twitter with wget, which may be handy for other automation projects):</p>
<pre>#!/bin/sh
MB_POST="http://identi.ca/api/statuses/update.xml
  http://twitter.com/statuses/update.xml"

MB_USER=<span style="color: #800000;">state your username</span>
MB_PASS=<span style="color: #800000;">state your password</span>

IZ="$(find Maildir/cur/ Maildir/new/ -type f | wc -l)"
if [ $IZ -gt 0 ]; then
 Â IZ="$IZ"
else
 Â IZ="ZERO"
fi
IZ="inbox zero status: $IZ"

for MB_HTTP in $MB_POST; do
  wget -qO- --delete-after \
    --user="$MB_USER" --password="$MB_PASS" \
    --post-data "status=$IZ" $MB_HTTP &gt; /dev/null
done</pre>
<p><strong>Update:</strong> Fixed script to use any Twitter-style microblog API, and included example URL from <a href="http://identi.ca/">identi.ca</a>. Go freedom!</p>
<p><strong>Update:</strong> Even better, just post to all of them at once! Also fixed anchor&#8230; Despite switching to the visual editor weeks ago, I&#8217;m still not 100% used to the convenience of it. <img width='16' height='16' src='http://bethesignal.org/wp-content/plugins/tango-smilies/tango/face-wink.png' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://bethesignal.org/blog/2008/07/23/inbox-zero-status-zero/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Fail We Can Believe In</title>
		<link>http://bethesignal.org/blog/2008/07/22/fail-we-can-believe-in/</link>
		<comments>http://bethesignal.org/blog/2008/07/22/fail-we-can-believe-in/#comments</comments>
		<pubDate>Tue, 22 Jul 2008 03:15:51 +0000</pubDate>
		<dc:creator>Jeff Waugh</dc:creator>
				<category><![CDATA[Asides]]></category>
		<category><![CDATA[Barack Obama]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[fail whale]]></category>
		<category><![CDATA[Obama]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://bethesignal.org/?p=1088</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><img style=' display: block; margin-right: auto; margin-left: auto;'  class="size-full wp-image-1089 aligncenter" title="Twitter's Fail Whale vs. Barack Obama's Change Wail" src="http://bethesignal.org/wp-content/uploads/2008/07/fail-we-can-believe-in.png" alt="Fail We Can Believe In" width="500" height="602" /></p>
]]></content:encoded>
			<wfw:commentRss>http://bethesignal.org/blog/2008/07/22/fail-we-can-believe-in/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
	</channel>
</rss>

