"Michael Brown" <[EMAIL PROTECTED]> wrote on 16-6-2003 15:39:42: > >> If I make a portal and choose an official client for it (and call it >> exactly that), there's nothing you can do about it. It's very >> unfortunate if that would piss you off (for you), but I don't see any >> reason why it should upset you in the first place? The choice of >> client in Jabber is not limited to the end-user. The provider of the >> server has the same right of choosing a client. And yes, it can go >> hand in hand with promotion of Jabber. Tipic comes to mind as an >> example. > >Sure. Your website - you get to choose whatever client you like. Why >would I have a problem with that? I think you misunderstand me...
Rachel Blackman writes for example: >> On my server Psi is the "official client". There are downloads that >> bundle Psi with fitting SSL certificates for this server, with >> localization resources and some additional icons. There is a small >> introduction on how to set up Psi. So, "Psi" is the "official >> client" for jabber.fsinf.de, if you like to say so. Most users of >> this server use Psi and seem satisfied. > >This is exactly the sort of example I meant in terms of an 'official >client'. It doesn't have to be for all of Jabber, just for whatever >this system is. You respond to this: "Michael Brown" <[EMAIL PROTECTED]> wrote on 16-6-2003 15:39:42: > >> >Rachel - seriously, drop the term "Official Client" - please. That >> >is really going to start pissing off other client developers >> >(starting with me). Maybe you're the one who is misunderstanding something? -- Tijl Houtbeckers Software Engineer @ Splendo The Netherlands _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
