#5 decentral ip.to.ip messenger integation

[Anonymous]

Hi
please explore this messenger, as it is fully decentral
and has encrypted transfers for messages and files.
The messenger is closed source and in c++.

It needs no central server and the isp is, so it is
reported, as well excluded because of the encryption.

Please test this: because of the encryption: if it is a
direct point to point encryption which means as well a
end to end encryption, how could the Isp excluded and
the key for the enxcryption transferred safe, if it is
the same line ?

Eric, is it possible to have the same architecture in
jeti?

this means a ip-to-ip messenger, which is adiitonally
handled,

and: if there is a handshake between two aol users, and
the IP of both is known, that then the decentral
protocol is used ?

this means that the aol connectionhandshake is ONLY
used for bootstrapping hte iP adress and then all other
transfers are handled over the ip-to-ip (wihtout
server) transfer ?

The interesting thing for cipher messenger is, that it
supports dynamic ip adresses, because both ip adresses
are saved in both participants, the one is found, if
the other changes the IP dynmically.

So only one needs to be Still online or have a stable
IP.

Only in the case both buddies were offline and get a
new IP the Buddy is lost.

This system is highly recommended for jeti.

http://www.brooksyounce.com/soft-SuperCipher4.htm

[Eric de Boer]

Logged In: YES
user_id=1169933

Jeti is a jabber client, so it uses a jabber server.
The nice thing about jabber is that only the server know
your ip adres and not everyone on your contact list. I do
not see any advantage in a p2p way to chat, only disadvantages

You might add a jabber server to each client and make a p2p
network with that, but then you can offcourse just as well
take a native p2p chat client

[Matej Cepl]

and why is this invalid ticket not closed?