[jdev] Re: CSpace instant messenger integrated in Jabber / GAJIM

Michal vorner Vaner michal.vaner at kdemail.net
Sat Aug 5 04:14:56 CDT 2006

On Sat, Aug 05, 2006 at 12:00:17AM +0200, thomasasta at gmx.net wrote:
> Hi
> 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.

You do not seem to understand purpose of jabber. Why is cspace something
so special we should care more than with other IM networks?

Between, try meet someone ask him to dictate you his public key ;-). I
remember my JID.
> 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.

Well, is it possible to run more your clients on a same computer with
separate keys? Like on a unix system, two logged-in people, having each
his own? If no, then I think your system is broken.

If yes, why could not the transport have all the private keys of the
users (OK, it is not too much secure, I know, but no transport is, you
have to give it at last password or so..) and act as many clients on the
same machine?
> 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.

I want to see all these jabber-only clients do that :D. That just makes
no sense. Being you, I would ask the multiprotocol ones.
> 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 RSA-Key.
> this means only the cleints can get hybrid with Cspace.
IMHO they can not get hybrid. Implementation and religious reasons.
> 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.
Um, and where would all the transports, all the services, dictionaries,
offline storages go? No, you made entirely _new_ protocol, that does not
have much to do with jabber. Jabber is server-oriented. You can hardly
turn it inside out. You can get inspired and define a new protocol.

Between, speaking about redefining protocols, you should go to JIG, not
> And for this purpose each client needs to implement CSpace, or lets say more freindly kademlia (but kompatible with Cspace)... Like Emule implemented Kademlia.
> understood the revolution/turnaround?
If you asked me, this will not fly. You need to persuade all jabber-only
clients to include cspace. They will say "Um, why? Another foreign
network, we do not care." And you need to define some binding between
jabber and cspace. 

Between, even this approach has some disadvantages by itself. You can
not just go to friends computer and log on by name and password you 
remember. Do you have contactlist that you would download each time you
log in? Do you support offline messages? Normal users just do not care
about security. That is why they still use networks like MSN or ICQ,
they are totally unencrypted.
> 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.
> Thanks
> -------- Original-Nachricht --------
> Von: "Jeffrey C. Ollie" <jeff at ocjtech.us>
> > I would recommend looking at PyMSNt and PyICQt for inspiration:
> > 
> > http://delx.cjb.net/pymsnt/
> > http://pyicq-t.blathersource.org/
> Von: "Norman Rasmussen" <norman at rasmussen.co.za>
> > 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/
> >
> > On 8/4/06, thomasasta at gmx.net <thomasasta at gmx.net> wrote:
> > > 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" <jeff at ocjtech.us>
> > > 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, thomasasta at gmx.net 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

This is a terroristic email. It will explode in 10 minutes, 
if you do not close it in the meantime.

Michal "vorner" Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20060805/d77305c9/attachment-0002.pgp>

More information about the JDev mailing list