🚀 go-pugleaf

In article <1991Apr30.162306.3744@cica.indiana.edu> mr@ogre.cica.indiana.edu (Michael Regoli) writes:
>In <1991Apr27.005127.15710@agate.berkeley.edu>
>magid@sandstorm.Berkeley.EDU (Paul Magid) writes: 
>
>>It strikes me as being a good idea to have a list of all new uploads to 
>>cica.  I do believe that the site is moderated and the service would
>>not be too much effort, and I would benifit users greatly.
>
>>Paul
>
>Speak for yourself!  :)
>
>If you are running Unix, you can create your own list of recent
>uploads from the INDEX file.
>
>The following set of commands will give you the most recent ten
>uploads to cica.  (This doesn't include those files in the "uploads"
>directory since we don't catalog them into the INDEX file until
>they've been placed in the proper location.)
>
>grep -v \* INDEX | sed -e 's/\n//' | awk '{print $2, $1}' | sort -rn | head -10
>
>Ugly, eh?
>
>I don't think posting this would be a benefit to anyone.  Those with
>ftp access normally get a copy of the INDEX on a daily basis anyway.
>
>--
>
>michael regoli
>mr@cica.indiana.edu
>regoli@iubacs.BITNET
>..rutgers!iuvax!cica!mr

Now speak for YOURSELF!

I don't mean to flame, but I have ftp access and I only check cica
every week or so -- I don't have enough time or need to check daily.  
I don't think that UNIX command a)is particularly rememberable for
everyone (OK, I could make it into a script, but I'm not sure how to
do so.), and b)isn't useful if there have been more than 10 new
downloads!  

If you, as the cica administrator (I believe you are, right?) believe
that putting together an update index every time you make changes to
the INDEX (simply listing the changes, perhaps) would be a pain in the
butt, then say so.  Personally, I feel that it would benefit a lot
more people than you seem to think.

Obviously, the decision is yours, but I think you are using faulty
reasoning there.

Adam Elman
elmanad@leland.stanford.edu