thanks for the suggestions. As said, I think a gateway in http://Cspace.in is 
not necessary, as we mix up secure and insecure chats and Cspace needs other 
development than multiprotocol, though, other jabber clients should integrate 
Cspace, either as a code to get a multiclient or with a transport. The 
suggestions are quite fitting, but I think you did not get th earchitecture of 
CSpace, so test around please.

The messenger is a p2p decentral messenger based on a kademlia dht.
All is encrypted in secure channels.
This means creating a transport is quite impossible, we would need one 
transport server, forwarding the message from jabber user to the C-Space 
ID-User, this means e.g. several users get from the same server the RSA-Key as 
the sender (forwarder) of the message. This would mix up the system, so only 
the client can integrate CSpace as a hybrid version.

This is requested and recommended, and if two users could switch to cspace in 
Jabber to jabber client, than they should leave jabber for secure Cspace 
protocol... of course this is very acid to jabber as here a leave of the jabber 
identity is necessary...  But otherwise I see ne technical solution, if you 
have no idea to this problem.

So how could a jabber transport be organized in to a p2p system ???
The transport server then needs to deliver all messages to a certain RSA-key, 
found on the kademlia dht. And this means, that eihter the server or the jabber 
client needs to get a RSA-Key too.

But for a server this makes no sense, as then there is only one KEY for several 
users as said, and then we are again at the model, that every client needs a 

this means only the cleints can get hybrid with Cspace.

There was a long time ago the question for encrypted jabber, why we need 
servers, if they route white node traffic, they cannot read. So a server 
architecture of encrypted messages is nonsense and they could to it IP to IP. 
They only need a lookup service to get the IP adress or RSA-key of the client.

Once this understood, with the first coded p2p Messenger, which is now out with 
CSpace, we can get rid of the jabber servers.

This lead to a total re-definition of jabber, and we do not need jabberservers 
anymore. As this is as well the jabber developer list, I want to make the 
discussion more wider to change the Jabber brand to Cspace protocol and clients.

*THIS* must be jabber. Jabber needs to get rid of the servers, as emule with 
kademlia has as well the option to work without servers.

And for this purpose each client needs to implement CSpace, or lets say more 
freindly kademlia (but kompatible with Cspace)... Like Emule implemented 

understood the revolution/turnaround?

We need RSA-Key´s not jabberservers in the announcement of Messenger profiles. 
So this needs to be discussed in the next jabber conference and we need the 
first python clients getting hybrid with Cspace as this is the most easiest to 
start with python written jabber clients.


-------- Original-Nachricht --------
Von: "Jeffrey C. Ollie" <[EMAIL PROTECTED]>

> I would recommend looking at PyMSNt and PyICQt for inspiration:
> http://delx.cjb.net/pymsnt/
> http://pyicq-t.blathersource.org/

Von: "Norman Rasmussen" <[EMAIL PROTECTED]>

> Sounds like something, someone with some twisted or xmpp.py experience
> (and some time) could look at.
> http://twistedmatrix.com/trac/
> http://sourceforge.net/projects/xmpppy/

> > ok, IMHO Cspace does not need multiprotocol,
> >
> > how do we get in jabber a transport for the new messenger
> >
> > http://cspace.in
> >
> > then ?
> >
> > -------- Original-Nachricht --------
> > Datum: Fri, 04 Aug 2006 14:05:33 -0500
> > Von: "Jeffrey C. Ollie" <[EMAIL PROTECTED]>
> > Betreff: Re: [Gajim-devel] p2p python instant messenger integrated in
> GAJIM     (pyhton)
> >
> > > I can't speak for the developers, but from what I know of Gajim it
> isn't
> > > aspiring to be a multiprotocol instant messaging client.  Gajim gets
> > > it's ability to talk to users on other instant messaging networks by
> > > using the Jabber/XMPP protocol to talk to special gateways (known as
> > > transports).
> > >
> > > CSpace users could use a similar method to connect to other instant
> > > messaging services from the native CSpace client.
> > >
> > > I'd also suggest creating a CSpace plug-in for Gaim.  Gaim is designed
> > > to support many different instant messaging protocols through the use
> of
> > > plugins.
> > >
> > > On Fri, 2006-08-04 at 19:39 +0200, [EMAIL PROTECTED] wrote:
> > > >
> > > > there is a new p2p serverless Instant Messenger out:
> > > > Open, Pyhton, excrypting everything.
> > > >
> > > > Would it be possible that GA JIM developers integrate this Messenger
> > > Protocol and system / Gui as well in GAJIM ??
> > > >
> > > > Then Cspace users, which need a gateway to AOL MSN JAbber etc, could
> use
> > > GAJIM. And the CSpace Developers could keep the Cspace free from
> > > GATEWAYS,w hich woudl only bloat their software now, as we need a
> secure only
> > > environment and a Cspace only client.
> > > >
> > > > So Gajim with Cspace support would be perfect, maybe you could have
> a
> > > look at the python code and integrate it in Gajim,
> > > >
> > > > here is the website, see as well the Trac-Wiki with Suggestions and
> the
> > > Mailinglist about the gateways...
> > > >
> > > > http://Cspace.in
> > > >
> > > > if you want to contact the developers, use the CC mailers.
> > >
> >
> > --

Echte DSL-Flatrate dauerhaft für 0,- Euro*. Nur noch kurze Zeit!
"Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl
Gajim-devel mailing list

Reply via email to