<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Jeff Licquia's (old) Blog</title>
    <link>http://www.licquia.org/log/</link>
    <description>Yet another Blosxom weblog.</description>
    <language>en</language>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <generator>blosxom/2.1.2</generator>

  <item>
    <title>Straw as a Necho Aggregator</title>
    <pubDate>Sun, 06 Jul 2003 07:41:00 +0000</pubDate>
    <link>http://www.licquia.org/log/2003/07/06#2003-07-06_02-41</link>
    <category>/jeff</category>
    <guid isPermaLink="false">http://www.licquia.org/log/jeff/2003-07-06_02-41</guid>
    <description>&lt;p&gt;
As everyone knows who&apos;s read the &lt;a href=&quot;/about.shtml&quot;&gt;about page&lt;/a&gt;,
this site uses weblog technology to do its magic.  Weblog technology is
moving very quickly at the moment, and there&apos;s 
&lt;a href=&quot;http://www.intertwingly.net/wiki/pie/FrontPage&quot;&gt;a new effort
out there&lt;/a&gt; to more clearly define what it&apos;s all about.  The project
started out as &quot;Echo&quot;, but it turns out that other software uses that
name, so the current working names seem to be &quot;(not) Echo&quot; or &quot;Necho&quot;. 
I&apos;ll stick with the latter for now.
&lt;/p&gt;
&lt;p&gt;
The project has decided to start 
&lt;a href=&quot;http://www.intertwingly.net/blog/1506.html&quot;&gt;calling for
implementations&lt;/a&gt; of the current preliminary spec for the syndication
feed: the part that does the job of RSS.  Most of the emphasis so far
has been on developing the feeds themselves, or of translating the feeds
into various formats.  To my knowledge, no one has hacked any of the
software that reads these feeds to read Necho feeds.
&lt;/p&gt;
&lt;p&gt;
At least, that is, until now.
&lt;/p&gt;
&lt;p&gt;
I&apos;ve been playing around with the 
&lt;a href=&quot;http://www.nongnu.org/straw/&quot;&gt;Straw&lt;/a&gt; news aggregator for 
&lt;a href=&quot;http://www.gnome.org/&quot;&gt;the GNOME desktop&lt;/a&gt;.  It&apos;s written in
Python (yay!), and is rather well-written; the source is easy to work
with.  This seemed like a good opportunity for me to contribute to the
Necho project and to learn a little about how Straw works at the same
time.
&lt;/p&gt;
&lt;p&gt;
The patch is 
&lt;a href=&quot;/code/straw-0.18.1-necho-0.1-patch.diff&quot;&gt;here&lt;/a&gt;.  (Please be
kind to my poor server!)  It&apos;s a patch against Straw 0.18.1, which can
be downloaded from 
&lt;a href=&quot;http://savannah.nongnu.org/download/straw/straw.pkg/0.18.1/straw-0.18.1.tar.gz&quot;&gt;here&lt;/a&gt;.
Unfortunately, Straw only runs on systems with GNOME, which means only
Linux, the BSDs, and other UNIXes; sorry, Windows users.  It seems to do
pretty well with the Necho feeds I&apos;ve tried out, including Sam&apos;s 
&lt;a href=&quot;http://intertwingly.net/stories/2003/07/01/example.necho&quot;&gt;original
test feed&lt;/a&gt; and feeds from 
&lt;a href=&quot;http://www.joelonsoftware.com/echo.xml&quot;&gt;Joel Spolsky&lt;/a&gt;, 
&lt;a href=&quot;http://philringnalda.com/feed.xml&quot;&gt;Phil Ringnalda&lt;/a&gt;, and
&lt;a href=&quot;http://diveintomark.org/xml/necho-prototype-20030701.xml&quot;&gt;Mark
Pilgrim&lt;/a&gt;.  There are a few quirks; it seems to like using the current
time as the last modified time for all posts, for example.  I also
haven&apos;t added handling for authors and contributors, because this
involves a level of XML tag nesting that the current handlers don&apos;t
handle well yet.
&lt;/p&gt;
&lt;p&gt;
I&apos;ll try to do my best to keep this up to date, but it&apos;s possible that
other projects and real life may consume my time for working on this. 
At the very least, this should provide a starting point for testing
Necho&apos;s interaction with news aggregators.  Comments to this log entry,
or E-mail to &quot;jeff+straw&quot; at &quot;licquia.org&quot;, are appreciated.
&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Happy Fourth!</title>
    <pubDate>Sat, 05 Jul 2003 00:27:00 +0000</pubDate>
    <link>http://www.licquia.org/log/2003/07/05#2003-07-04_19-27</link>
    <category>/news</category>
    <guid isPermaLink="false">http://www.licquia.org/log/news/2003-07-04_19-27</guid>
    <description>&lt;p&gt;
Before the big storms, we went to the Independence Day celebration in
Carmel, the town west of us.  Carmel has a government center with an
elaborate City Hall and a large fountain and sitting area in front.  For
CarmelFest, the city blocks off the whole area, sets up a stage for live
music, has fair-style vendors and local groups set up shop, sets up
games and activities behind City Hall, and opens the fountain to
swimming.
&lt;/p&gt;
&lt;p&gt;
We don&apos;t know if there will be fireworks tonight, but if so, we&apos;ll
probably go downtown to see them, just like we did last year.  As family
traditions go, our Fourth routine is pretty good.
&lt;/p&gt;
&lt;p&gt;
We hope you have a happy Fourth as well.  Post some comments if you did
anything interesting.
&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Being noticed, CSS, RSS</title>
    <pubDate>Thu, 26 Jun 2003 06:12:00 +0000</pubDate>
    <link>http://www.licquia.org/log/2003/06/26#2003-06-26_01-12</link>
    <category>/jeff</category>
    <guid isPermaLink="false">http://www.licquia.org/log/jeff/2003-06-26_01-12</guid>
    <description>&lt;p&gt;
Motivated by &lt;a href=&quot;/log/jeff/2003-06-23_16-25.writeback&quot;&gt;the problems
I&apos;ve been having with weblog tools&lt;/a&gt;, I put some effort into the Web
site.  There&apos;s a new CSS-only layout; all tables have been banished. 
I&apos;ve switched to pinging &lt;a href=&quot;http://blo.gs/&quot;&gt;blo.gs&lt;/a&gt;; they seem
to be more flexible in following the sites.  So far, it seems to
updating; we&apos;ll see with this post.
&lt;/p&gt;
&lt;p&gt;
Those people who use RSS should note that the RSS links have changed. 
The old ones are still supported (and should be for the foreseeable
future), but we&apos;ve now got spiffy new RSS 2.0 feeds as well.
&lt;/p&gt;
&lt;p&gt;
Finally, those people who like the pictures on the site home can
rejoice.  I&apos;ve finally fixed the last bug on the auto-picture-post
system for &lt;a href=&quot;&quot;&gt;our new picture phones&lt;/a&gt;, so we can upload a
picture to the site directly from our phones.  This should increase the
likelihood that we&apos;ll update the pictures more frequently.
&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Site layout changes</title>
    <pubDate>Thu, 26 Jun 2003 06:03:00 +0000</pubDate>
    <link>http://www.licquia.org/log/2003/06/26#2003-06-26_01-03</link>
    <category>/news</category>
    <guid isPermaLink="false">http://www.licquia.org/log/news/2003-06-26_01-03</guid>
    <description>&lt;p&gt;
We&apos;ve got a new layout.  It&apos;s very close to the old layout, but you can
see it if you look closely.  The main difference: no tables, which is a
lot easier to work with on the backend.
&lt;/p&gt;
&lt;p&gt;
There are quite a few changes behind the scenes, too.  Let us know in
the comments if you have any problems.
&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Not getting noticed anymore</title>
    <pubDate>Mon, 23 Jun 2003 21:31:00 +0000</pubDate>
    <link>http://www.licquia.org/log/2003/06/23#2003-06-23_16-25</link>
    <category>/jeff</category>
    <guid isPermaLink="false">http://www.licquia.org/log/jeff/2003-06-23_16-25</guid>
    <description>&lt;p&gt;
Most of the cool blog tools out there rely on one of two services to
know when to check a blog for new information: 
&lt;a href=&quot;http://weblogs.com&quot;&gt;Weblogs.com&lt;/a&gt; and 
&lt;a href=&quot;http://blo.gs&quot;&gt;blo.gs&lt;/a&gt;.  As far as I can tell, each services
also watches the other, so you only have to update one service for
everyone to get notified.  I update Weblogs.com because there&apos;s a native
Blosxom module for doing this that does its thing automatically.
&lt;/p&gt;
&lt;p&gt;
So, when it seemed that &lt;a href=&quot;http://technorati.com/&quot;&gt;Technorati&lt;/a&gt;
wasn&apos;t paying attention to links I&apos;ve made to other bloggers, I got
suspicious that my Weblogs.com pings weren&apos;t happening.  Sure enough,
blo.gs (which has a search function) doesn&apos;t think my blog has updated
since the 16th.  Looking at the last ping, it appears that Weblogs.com
is actually trying to verify an update, rather than just taking my word
for it, and the verification is failing.
&lt;/p&gt;
&lt;p&gt;
This makes sense, in a way.  The front page of this site only contains
the full stories for one section of the blog: the news stories.  My
section and Tami&apos;s are in the sidebar, but only with post titles.  I did
it this way because I didn&apos;t want to inflict my rants on people who just
wanted to know how the family was doing.  (Incidentally, you can see all
three sets of posts munged together with &lt;a href=&quot;/log/&quot;&gt;this link&lt;/a&gt;. 
I don&apos;t generally advertise or support it, but it&apos;s there all the same.)
&lt;/p&gt;
&lt;p&gt;
This way of laying things out made sense to me, and works from a
browsing perspective, but doesn&apos;t work from the point of view of these
new tools.  Clearly, I need to reorganize things to be cooperative with
non-browsers.  The best thing, I think, is to split the two personal
logs from the main one, and report different addresses to Weblogs.com
for those.
&lt;/p&gt;
&lt;p&gt;
So don&apos;t be surprised if things start changing around here.
&lt;/p&gt;
</description>
  </item>
  </channel>
</rss>
