[lilycore-dev] Re: Depermitted discussions should not be "destroyed". (PR#532)

[Christian R. <lil...@ce...>]

Jack,

  The behaviour you describe is by design. When you are depermitted from a
discussion, it ceases to exist for you. For that reason a destroy notification
is the most accurate representation of what occured. If you are permitted to a
private discussion, or your ban is lifted from a public discussion, then a
permit event is also the best description of what took place since the
discussion is not, in fact, newly created.
  While one could easily argue at length that a depermit should make clear to a
user they have been kicked out, such is not the design of lily. The point
remains, nonetheless entirely valid, and for a different CMC the solution
proposed here may be quite applicable. A good idea remains a good idea even if
it does not fit within the current design criteria.

christian

> User: [#157] nautilus
> MOO: 1.8.1+g1+s
> Core: lily running rev 2.6.2
> Server Time: Fri Nov 15 16:00:56 2002 EST
> ---%report%----
> A discussion which is not joined by a user and is then depermitted
> to that user causes a "destroy" event to be sent.  When this discussion
> is then repermitted, a "permit" event is sent.  This is broken as either
> both create and destroy or permit and depermit should be used, not mix
> and match.  
> ---%report%----
> 
>