[NNTP] LISTGROUP

[Peter Robinson]

Russ Allbery <rra at stanford.edu> wrote:

> Clive D W Feather <clive at demon.net> writes:
> 
> > I've just remembered something else that falls into this category.
> 
> > Can we make the parameter to GROUP be optional? The effect of omitting it
> > would be:
> > * If there is a currently selected group, the same as if it were specified.
> > * If there is no currently selected group, a 412 error.
> 
> > The purpose is to allow the client to determine the currently selected
> > group.

Interesting!

[...]

> This is feeling like we're falling down a slippery slope of last-minute
> changes to me.

Yes.

> I was willing to pursue LISTGROUP because a few client authors went "this,
> this I want to use" when the idea was raised.  Do we have a similar
> feeling with this addition, or is it just in there for cleanliness?

My feeling is that it's a shame it's not always been available and it
fits snugly into the GROUP command, but that it's probably not worth
adding another subtle incompatibility now.  Having said that, if other
people want it, I won't argue against.

> My intuition says it would be very strange for a client to not know what
> its current group is.

I agree.

Regards,

Peter