Well sorry at first for generating that "bug", I seemed to miss some deeper
thinking about it before, until Vivia told me that it should be a feature.
Maybe I translated my commit comment a little bit too hard, I rather meant
some kind of security risk instead of vulnerability, sorry for that, too.
Logout usually means you want to quit *all* your personal matters and not to
worry about several things that may be left. Windows won't leave some
instances of notepad open, for example, when you logout, or to compare it
with the online banking example of Harry: What if your online banking would
pop up a window with your statement, you simply click on logout and forget
to close the window with your statement. Sure, this window can't be simply
used to do unwanted things, but it is a lack of privacy. So it definitely is
a security risk for those who don't know of this feature, even me didn't
recognize that although using amsn for more than a year now. And I think the
users won't consist only of the devels here and some computer freaks that
use that feature actively, there will be a lot of "newbies" and I think you
are happy the more users will use your software. Furthermore it could also
happen that you simply forget closing a window (that is minimized for
example), especially when amsn is not the only program running, nobody is
perfect! So this is some kind of userfriendlyness to give users the feeling
of security and not to have to care for themselves, even users are lazy, you
should remember that! I can understand, you used that feature long time and
that you get angry that I didn't think of the possibility that this could be
a feature and only thought of the new users and this security risk, but I
think, the solution you proposed, and I implemented then, would be a
compromise, to allow the user choosing between the feature and the safety of
their privacy.
If you really can't share my thoughts and disagree on that, I'll revert it
...

Mirko


2007/7/30, Youness Alaoui <[EMAIL PROTECTED]>:
>
> Hi Harry,
> First, I wasn't yelling, I don't think I yelled and if I did, I'm sorry,
> it wasn't my intention, all I said was that features like that should be
> discussed, and that I just lost all my
> CWs and I was :(
> about the discussion, lol, I should really see a doctor, I even answered
> on that thread :p and I got no memory about that...
> so yeah, it was discussed before, but indeed, we never decided to do it.
> Anyways, I stop hope the change will be reverted... although I saw some
> other commits after that related to this bug, so maybe Baazen fixed it
> somehow..
>
> KKRT
>
>
> On Mon, Jul 30, 2007 at 07:37:49PM +0200, Harry Vennik wrote:
> > Youness, I think there is no reason to yell that much. There were a
> > few e-mails about this, although this exact behavior was not agreed
> > upon. But it might be just a wrong implementation of what was
> > discussed. So, still a BUG, but no need for saying there hasn't been
> > any discussion. (FYI: discussion was in reply to commit of rev. 8929).
> >
> > Harry
> >
> > Op 30-jul-2007, om 19:10 heeft Youness Alaoui het volgende geschreven:
> >
> > > yeah, it's a BUG!!
> > > Baazen... your latest changes made all chat windows close on
> > > logout... WHY?
> > > I don't think it's a good idea, and it's also a change in behavior
> > > which should have been discussed on the mailing list, and I didn't
> > > get any
> > > email..
> > > unless SF screwed up and I don't get any more emails from the ML,
> > > otherwise, it's obvious that the ML is dead at the moment, but that
> > > doesn't mean
> > > we should just stop asking about features or others that should be
> > > put in SVN.
> > > Anyways, please revert your change since it just closed all my
> > > windows and I needed them to all stay opened while I was offline :@ :(
>
> > >
> > > Thanks,
> > > KKRT
> > >
> > >
> > > ----------------------------------------------------------------------
> > > ---
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a
> > > browser.
> > > Download your FREE copy of Splunk now >>   http://get.splunk.com/
> > > _______________________________________________
> > > Amsn-devel mailing list
> > > Amsn-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/amsn-devel
> >
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>   http://get.splunk.com/
> > _______________________________________________
> > Amsn-devel mailing list
> > Amsn-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/amsn-devel
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>   http://get.splunk.com/
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amsn-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Reply via email to