> 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.
