It's a far far cry between speaking HTTP and being a web browser. This whole conversation should really go offline or something, I find it funny that we've spent hundreds of messages deciding how to make shorthand work.
-----Original Message----- From: Dave [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 3:18 PM To: [EMAIL PROTECTED] Subject: Re: [JDEV] Emoticons: guidelines It may be silly for a Jabber client to be a Web browser, but the standard OOB method in Jabber is HTTP, so any Jabber client that wants to support file transfer already is a Web browser. It may be silly, but it's true ;-) - Dave Richard Dobson wrote: > > ----- Original Message ----- > From: "Dave" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, April 23, 2002 11:53 PM > Subject: Re: [JDEV] Emoticons: guidelines > > > > Also why mention web browsers, jabber is not a web browser ??? > > Jabber clients that download images off the 'net had better be (or be > > able to talk to) web browsers. Else, it'll be rather hard for them to > > fetch the images. > > Urm rigghtt so now you are saying that jabber clients either should be a web > browser (isnt it supposed to be an im client ???), or rely on a external web > browser to even function. > > Now this is just getting silly. > > Rich > > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev