X-Git-Url: http://git.bytex64.net/?a=blobdiff_plain;f=www%2Fdoc%2Findex.html;h=5a170e6d7cd596db930a9612b9f8cd24c2e6cc30;hb=a88ac56feb7930b575668d20f31285d83da95893;hp=21982bd108abaf79adb59c0f5b8dbfeda613f9a9;hpb=dfd9f2ccb8a86e20401c2d789bd4152786484024;p=blerg.git

diff --git a/www/doc/index.html b/www/doc/index.html
index 21982bd..5a170e6 100644
--- a/www/doc/index.html
+++ b/www/doc/index.html
@@ -39,7 +39,7 @@ C.
       <li><a href="#api_subscribe">/subscribe/(user) - Subscribe to a user's updates</a></li>
       <li><a href="#api_unsubscribe">/unsubscribe/(user) - Unsubscribe from a user's updates</a></li>
       <li><a href="#api_feed">/feed - Get updates for subscribed users</a></li>
-      <li><a href="#api_feedinfo">/feedinfo/(user) - Get subscription status for a user</a></li>
+      <li><a href="#api_feedinfo">/feedinfo, /feedinfo/(user) - Get subscription status</a></li>
     </ul>
   </li>
   <li><a href="#design">Design</a>
@@ -86,10 +86,15 @@ sense of humor, requires ruby to compile)</li>
 
 <h3><a name="configuring">Configuring</a></h3>
 
-<p>I know I'm gonna get shit for not using an autoconf-based system, but
-I really didn't want to spend time figuring it out.  You should edit
-libs.mk and put in the paths where you can find headers and libraries
-for the above requirements.
+<p>There is now an experimental autoconf build system.  If you run
+<code>add-autoconf</code>, it'll do the magic and create a
+<code>configure</code> script that'll do the familiar things.  If I ever
+get around to distributing source packages, you should find that this
+has already been done.
+
+<p>If you'd rather stick with the manual system, you should edit libs.mk
+and put in the paths where you can find headers and libraries for the
+above requirements.
 
 <p>Also, further apologies to BSD folks &mdash; I've probably committed
 several unconscious Linux-isms.  It would not surprise me if the
@@ -304,15 +309,26 @@ a user's updates</h3>
 
 <p>POST to /feed, with a <code>username</code> parameter and an auth
 cookie.  The server will respond with a JSON list of the last 50 updates
-from all subscribed users, in reverse chronological order.
+from all subscribed users, in reverse chronological order.  Fetching
+/feed resets the new message count returned from /feedinfo.
 
 <p>NOTE: subscription notifications are only stored while subscriptions
 are active.  Any records inserted before or after a subscription is
 active will not show up in /feed.
 
-<h3><a name="api_feedinfo">/feedinfo/(user)</a> - Get subscription
+<h3><a name="api_feedinfo">/feedinfo, /feedinfo/(user)</a> - Get subscription
 status for a user</a></h3>
 
+<p>POST to /feedinfo with a <code>username</code> parameter and an auth
+cookie to get general information about your subscribed feeds.
+Currently, this only tells you how many new records there are since the
+last time /feed was fetched.  The server will respond with a JSON
+object:
+
+<pre>
+{"new":3}
+</pre>
+
 <p>POST to /feedinfo/(user) with a <code>username</code> parameter and
 an auth cookie, where (user) is a user whose subscription status you are
 interested in.  The server will respond with a simple JSON object: