From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rss replacement
Date: Tue, 8 Aug 2006 10:44:56 -0700 [thread overview]
Message-ID: <4966bd94937e3fa7df0e658b7aa9ab30@9netics.com> (raw)
In-Reply-To: <20060808173413.GI29618@wmii.de>
>> Aside from not using XML, how would a plan9-ish RSS replacement look
>> different from RSS?
>
> I think cat(1) and ls(1) would do the job quite fine, assumed
> that the filename correponds to a headline, and the file
> contents contain the associated document...
yep. and no pushing, that means the content is always fresh
because you're getting it from the source (via aggregators).
could also build a Mail (acme interface not upas) ui to it.
authentication could follow russ' model for sources; readers
can be 'none' and syndicators require a login.
syndication is done with either exportfs or a "drawterm" like
gizmo from other os.
next prev parent reply other threads:[~2006-08-08 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 0:57 Skip Tavakkolian
2006-08-08 17:18 ` Micah Stetson
2006-08-08 17:34 ` Anselm R. Garbe
2006-08-08 17:44 ` Skip Tavakkolian [this message]
2006-08-08 18:44 ` Christoph Lohmann
2006-08-08 19:21 ` Skip Tavakkolian
2006-08-08 17:55 ` Micah Stetson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4966bd94937e3fa7df0e658b7aa9ab30@9netics.com \
--to=9nut@9netics.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).