From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <e90bac8e5f3dd93222c937c81c9be247@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rss replacement
Date: Tue,  8 Aug 2006 12:21:40 -0700
From: Skip Tavakkolian <9nut@9netics.com>
In-Reply-To: <20060808204449.08543698.20h@r-36.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 9a3193d0-ead1-11e9-9d60-3106f5b1d025

> News(1) seems to be a good solution. What is needed, is a newsfs,
> that registers internally, when a entry was entered, so you are
> able to cp(1) one newfs to another and touch(1) is not able to
> bring up old news.

right, i forgot that /acme/news is already there; probably the right
start for the ui.

i'm not sure if you'd need news(1); if incoming (exported by other
plan9 or drawterm) 9news were posted to /srv/9news.$syndicator then
aggregation would be a matter of building the right ns.