<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: aaron-swartz</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/aaron-swartz.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2007-09-16T21:43:16+00:00</updated><author><name>Simon Willison</name></author><entry><title>Jottit</title><link href="https://simonwillison.net/2007/Sep/16/jottit/#atom-tag" rel="alternate"/><published>2007-09-16T21:43:16+00:00</published><updated>2007-09-16T21:43:16+00:00</updated><id>https://simonwillison.net/2007/Sep/16/jottit/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://jottit.com/"&gt;Jottit&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Aaron Swartz’s latest venture: a complete rethink of the Infogami concept. Well worth checking out for the extremely thoughtful way it introduces features, and the way account creation with a password remains optional until you want to add access control.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/aaron-swartz"&gt;aaron-swartz&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/authentication"&gt;authentication&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/bitbots"&gt;bitbots&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/infogami"&gt;infogami&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/jottit"&gt;jottit&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/usability"&gt;usability&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/userflow"&gt;userflow&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/wiki"&gt;wiki&lt;/a&gt;&lt;/p&gt;



</summary><category term="aaron-swartz"/><category term="authentication"/><category term="bitbots"/><category term="infogami"/><category term="jottit"/><category term="usability"/><category term="userflow"/><category term="wiki"/></entry><entry><title>ThingDB</title><link href="https://simonwillison.net/2007/Jul/17/about/#atom-tag" rel="alternate"/><published>2007-07-17T10:21:55+00:00</published><updated>2007-07-17T10:21:55+00:00</updated><id>https://simonwillison.net/2007/Jul/17/about/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://demo.openlibrary.org/about/tech"&gt;ThingDB&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Another extensible key/value pair data store, constructed for the Open Library based on Aaron Swartz’s Infogami technology.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/aaron-swartz"&gt;aaron-swartz&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/infogami"&gt;infogami&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/openlibrary"&gt;openlibrary&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/postgresql"&gt;postgresql&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/thingdb"&gt;thingdb&lt;/a&gt;&lt;/p&gt;



</summary><category term="aaron-swartz"/><category term="infogami"/><category term="openlibrary"/><category term="postgresql"/><category term="python"/><category term="thingdb"/></entry><entry><title>Hehe RSS3</title><link href="https://simonwillison.net/2002/Sep/7/heheRSS3/#atom-tag" rel="alternate"/><published>2002-09-07T14:34:29+00:00</published><updated>2002-09-07T14:34:29+00:00</updated><id>https://simonwillison.net/2002/Sep/7/heheRSS3/#atom-tag</id><summary type="html">
    &lt;p&gt;Forget about RSS 0.9x, RSS 1.0 and RSS 2.0, Aaron Schwartz has &lt;a href="http://www.aaronsw.com/weblog/000574"&gt;released a spec&lt;/a&gt; for RSS 3.0 :)&lt;/p&gt;&lt;blockquote cite="http://www.aaronsw.com/weblog/000574"&gt;&lt;p&gt;There's been a lot of talk in the community about how RSS 2.0 is too complicated. I haven't heard any objections, so I'm going to move ahead with the following changes that will result in RSS 3.0.&lt;/p&gt;

&lt;p&gt;1. Remove XML. XML is just too complicated and is against the spirit of RSS, which is Really Simple Syndication. I don't want people to have to buy one of these 200 page XML books to understand RSS. And XML sucks up bandwidth like nobody's business. Instead, we'll go back to RFC822-style fields. There are lots of available parsers for those.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;-- snip --&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;3. HTML forbidden. No one needs HTML. Email has been just fine for years before Microsoft introduce their stupid rich HTML extensions. HTML is for those loser newbies. Any intelligent Internet user deals in plain text.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;Best of all, it can be parsed using a &lt;a href="http://lists.w3.org/Archives/Public/www-archive/2002Sep/0089"&gt;Python one-liner&lt;/a&gt;.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/aaron-swartz"&gt;aaron-swartz&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/rss"&gt;rss&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="aaron-swartz"/><category term="rss"/></entry></feed>