From: nick G <nick6489@optonline.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: possible new Speakfreely project
Date: Sat, 03 Apr 2004 13:18:41 -0500 [thread overview]
Message-ID: <000901c419a8$17b40390$cc00a8c0@nickysp4> (raw)
In-Reply-To: <20040403171302.GB23618@gmx.net>
No, that opens ports as requested. I wouldn't mind that in Speak Freely
myself.
Thanks,
Nick
----- Original Message -----
From: "Alex Snow" <alex_snow@gmx.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, April 03, 2004 12:13 PM
Subject: Re: possible new Speakfreely project
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> upnp? or is that something else.
> On Sat, Apr 03, 2004 at 05:20:52PM
> +1000, Shaun Oliver wrote:
> > I heard tell that Alex Snow delivered up the following on Fri, Apr 02,
2004 at 06:42:15PM -0500,
> > > another thing that should be done to speakfreely is to improve it's
> > > nat support. I think this discourages the less knolageable users
> > > because they may not know how to modify router settings and such. This
> > > is why I've seen a lot of people use ventrilo because It's easy to set
> > > up network wise. if speakfreely supported this I think more people
> > > owuld use it.
> >
> > as I understand it, the reason that apps like yahoo's voice chat and
> > ventrilo are able to work without modifying router settings is because
> > the return path is sent out along with the data packet carrying the
> > audio so that various appliances inbetween the client and server or
> > other client can send it to the correct destination.
> > I did hear the correct term for this somewhere and I can't think of it
> > off the top of my head but yes it would be a great idea.
> >
> >
> >
> >
> > --
> > Shaun Oliver
> >
> >
> > "I refuse to have a battle of wits with an unarmed person."
> > email: shaun.oliver@optusnet.com.au
> > WEB: http://blindman.homelinux.org/~blindman/
> > IRC: irc.awesomechat.net:6666
> > IRCNICK: blindman
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> - --
> So in the future, one 'client' at a time or you'll be spending CPU time
with
> lots of little 'child processes'.
> -- Kevin M. Bealer, commenting on the private life of a Linux nerd
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD4DBQFAbvCd9XVrM3ri110RAjt/AJwPh/hE8NjtKT2XelokH+f/vCgPvwCWImnc
> AldVmAUCIDJ/vKuYaJJJjA==
> =eWF6
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Alex Snow
` Igor Gueths
` nick G
` Igor Gueths
` Alex Snow
` Igor Gueths
` Alex Snow
` Jared Stofflett
` Igor Gueths
` Shaun Oliver
` Alex Snow
` nick G [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='000901c419a8$17b40390$cc00a8c0@nickysp4' \
--to=nick6489@optonline.net \
--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).