On Tue, 25 Mar 2014 18:37:21 +0100
hiro <23h...@gmail.com> wrote:
> For IRC in general I would like to use something graphical, but
> sometimes I only have ssh, so I've only been using irssi in screen or
> tmux so far.
ssh is exactly one of the reason why ncurses makes sense.
If you design a clie
On Tue, 25 Mar 2014 18:11:47 +0100
hiro <23h...@gmail.com> wrote:
> does it show anywhere the rtp stream setup process including the
> hole-punching?
Not in the wiki sadly. Read the code.
--
FRIGN
On Mon, Mar 24, 2014 at 03:40:15PM +0100, Roberto E. Vargas Caballero wrote:
> > The new UTF-8 en-/decoder implementation patch is by Damian Okrasa, not by
> > me.
>
> Well, my suggestion was for him (I suck because I didn't explicitily said
> who was the listener).
>
> > If he doesn't mind thou
> IRC client <-> bitlbee <-> tox
Ah, so no voice over DCC. But I still don't like my IRC client, so I
don't know why you see value in that.
Anything interesting on top of sic or ii?
For IRC in general I would like to use something graphical, but
sometimes I only have ssh, so I've only been
>> XMPP starts with X, so it sucks, and SIP also has it's complexities if
>> you want...
>
> Dude, I have an epiphany right now ... XML, XSLT, X11,
Not to take all the credit: learned about the X principle somewhere on
cat-v.org (couldn't find it right now).
Greetings.
On Tue, 25 Mar 2014 18:11:10 +0100 hiro <23h...@gmail.com> wrote:
> > This is not a client for a mass market, but the masses can’t be saved.
> Then who are you going to talk to?
All the people via compatibility layers.
> > voice/video via DCC
> Does it work behind NATs. Why is DCC s
> Regarding the RTP stream, it's transported via UDP[0] (as usual).
does it show anywhere the rtp stream setup process including the hole-punching?
On March 24, 2014 12:20:49 PM CET, FRIGN wrote:
>Dude, I have an epiphany right now ... XML, XSLT, X11,
x86
On Tue, 25 Mar 2014 13:20:15 +0100
hiro <23h...@gmail.com> wrote:
> Sure, most DHT implementations work perfectly for signalling, as long
> as there are enough people without NAT helping out. But I don't see
> anything about the actual rtp stream there. Does it get sent over DHT,
> too? I see that
>> I would still want the application to fall back to using a proxy if
>> all hole-punching attempts failed. And what sadly is not obvious to
>> the implementers: I would want the applications to DETECT that it
>> failed, i.e. when there's no rtp packet for a second you send out some
>> standard SI
> I'm bored of discussing XMPP+SIP to be honest, when there are more
> interesting things like Tox in the making ;).
luckily for you the single implementations in either category differ
far more than the protocols+extensions.
> Have you checked retroshare?
they don't even list udp hole-punching,
11 matches
Mail list logo
