I certainly welcome this! :-)
> In addition, users will be able to adjust the number of events in
> a review buffer that are reserved for "special" events (currently
> defined as "public", "private", and "emote" events).
I assume this means in their own review buffers, and not the
buffers of discussions? What would this mean with respect to
discussion review buffers? (just curious).
> The syntax I anticipate using for the user interface is:
>
> /LIMIT [disc] [[RESERVE] count]
>
> /LIMIT acts upon the user's review buffer unless a discussion is
> specified.
I'm hoping that there will also be a limit based on age of the
events in the review buffer (at least for discussions). At RPI
I'd like to set it so events expired after one week, or maybe
two weeks.
> Any feedback on the proposed behavior of LIMIT would be appreciated.
Will we also get that "timestamp in the /review buffer" notification
that you had worked on for other lily servers?
This all sounds pretty good to me. It looks like I may have another
unexpected expense pop up here, and thus may not have money to spare
for big $$$ upgrades to support increased lily usage. Anything that
would reduce the memory usage of the server would be valuable to me.
Thanks! (and thanks for that idle-to-death bug-fix)
--- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu ITS Systems Programmer (handles NeXT-type mail) Rensselaer Polytechnic Institute; Troy NY USA