From: "Erik Heil" <eheil@rcn.com>
To: <speakup@braille.uwo.ca>
Subject: Re: Jabber console based clients
Date: Thu, 16 May 2002 20:16:36 -0400 [thread overview]
Message-ID: <008701c1fd38$1c0414f0$6401a8c0@6S4X011> (raw)
In-Reply-To: <015101c1fd34$2e3163c0$02263e18@mycomputer>
Hi Igor,
Actually, I was thinking about that. I'm not sure of what the current
status of console-based Jabber apps are, but I'm pretty sure that the
gateway only supports rudimentary text-only chat of course. i.e. No fansy
fonts because this would obviously involve some flags being client specific.
Wonder what they do in the case if their launched within an Xterm session?
Perhaps their as smart as Emacs and will communicate with the X server to
windowize the application and do all of the nice UI tricks that we expect in
GUI-enabled applications. While I'm on the subject of jabber and unified IM
gateways, I really don't see any hope for interoperable file transfers
unless perhaps some form of DCC would be implemented. After all, its taken
Microshaft and AOL so long to discuss the unified standard, and so far
nothing's been done. GRRRR!
----- Original Message -----
From: "Igor Gueths" <igueths@attbi.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, May 16, 2002 7:48 PM
Subject: Re: Jabber console based clients
Hey Erik. Ever think of a subset of the dcc functionality built into irc to
use as a file transfer protocol? That's what's its meant for anyway.
----- Original Message -----
From: Erik Heil <eheil@rcn.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, May 16, 2002 7:06 PM
Subject: Re: Jabber console based clients
> Hi,
> The only problem now is that some of the agents seem to be broken due to
the
> constant changes of protocols used by various IM applications. Hopefully
> this will change soon. Wonder why anyone from the start didn't have a
> standard for Unified IM's? Actually speaking of which, a subset of the
IRC
> protocol would work pretty nicely for basic functions. However for
> exchanging audio, somethinf more elaborate would need to be developed.
>
> ----- Original Message -----
> From: "Deedra Waters" <curi0315@tampabay.rr.com>
> To: <speakup@braille.uwo.ca>
> Sent: Thursday, May 16, 2002 6:06 PM
> Subject: Jabber console based clients
>
>
> > I'mc urious if any of you have suggestions for a jabber console based
> > client that I can use. I've tried imcom with verry little success. If
> > anyone has ideas, and how to get it working with the different jabber
> > agents I'd appreciate it.
> >
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Deedra Waters
` Erik Heil
` Igor Gueths
` Erik Heil [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='008701c1fd38$1c0414f0$6401a8c0@6S4X011' \
--to=eheil@rcn.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).