You may be right. For the same reason Youness said we should formalize the
meaning of the acronym amsn, but indeed that might not be enough. Also,
because we want to go multi-protocol some day, we may want to get that 'MSN'
out of our name. But: there are so many people that know the name
On Tue, Oct 10, 2006 at 07:18:02PM -0700, Jérôme Gagnon-Voyer wrote:
Ok, thx, I'm glad that YOU ARE STILLL ALIVEE... lol,
seriously though, the inactivity of the ML is
killing me...
No comment
--
I cannot find the email that explains why we should move out of
No, I really don't think the name should change... many, many users will not be
able to find us again if we do
that, also, 'amsn' is 'amsn'... the name should stay... but we should consider
'msn' as 'messenger' or any
other suitable acronym for that matter...
KKRT
On Wed, Oct 11, 2006 at
Ok, thx, I'm glad that YOU ARE STILLL ALIVEE... lol, seriously though,
the inactivity of the ML is
killing me...
anyways, thx for the answer.. I also like the amsn-messenger.net BUT, as I said
in an earlier email, to avoid
any problems with M$, we should officially name the product..
I hope amsn won't stay a project (do you want to change again the domain name with the 1.0 ? Or 2.0...) So I think amsn-messenger is better... However, maybe it's too long to write it... ... but I don't like amsn-team xD
So I said :+1 for amsn-messenger2006/10/11, Youness Alaoui [EMAIL PROTECTED]
Ok, thx, I'm glad that YOU ARE STILLL ALIVEE... lol, seriously though, the inactivity of the ML is killing me... No comment--I cannot find the email that explains why we should move out of sourceforge, especially for the main website. I'm really, really, really, really, affraid that now
