Hey Thom. > HEy Bob, you find my answers between the lines...
I just posted a long message on a board, which answers some of your questions about sharing with buddies: .... In the case of two seperate groups with one common peer: This peer will allow communication of Certificates/Signatures and Network Addresses, thus enabling peers from each group to connect to each other (if they choose). No other communication will take place at the moment. (might allow messages/chat in the future) > IMHO the one in both networks should be called GATEKEEPER. The download from > one network to the other should only work over partials, if the gatekeeper is > between buddies and peers (e.g. retroshare hybird wirth emule), if the > gatekeeper is between to buddies, then as well all shared files in the > library of one node are available for all buddies of this node, so for both > buddylists (which is for this node ONE buddylist) So if I join my buddylist for coworkers and my buddylist from family, then all coworkers can download from my family or even browse the nodes for the shared directory. If this system would be hybrid with edonkey, then the rule would be that I download a partial from edokey and all from my buddylist can download from that ed2k-partial. But emule nodes would not be able to download from shared files of my buddies. But If I download files from any buddy, this *partial* *MUST* be available for any emule node (golden rule for gatekeepers in a buddy-peer hybrid network). < It is far better to build the Trusted network first, then the anonymous network on top of it. > Cool idea, this is, what ants need to develop to. we need not 25 peers, we > need 20 trusted buddies and for the gatekeeper exchange (so that networks are > not redundant) there shoudl be a minimum-risk of some public peers in ants.. > this has been implemented in ants by the ejti buddylist, to first boostrap > ants and second to bootstrap ants with preferrred buddies. So all decentral with cspace in ants would be perfect. Buddybrowsing over retroshare and ed2k-link public sharing over ants would be a perfect system.. but non-direct flesharing like in ants in cspace added is too much and impossible, so maybe yes, let´s start with buddybrowsing in csapce... As Csapce has encryption we do not need Open SSL, just implement the function of file-Swarming of buddysharing with retroshare in cspace. Ask the developers for a joined team. < The other alternative is to merge it/collaborate with some other projects. I'm pragmatic and want the quickest route to success. So I'm very willing and able to make RetroShare work as a library within some other context. Or even cut out and integrate key bits with other interested parties. Any Developers looking for an Interesting Project to work on? or any Projects looking for collaboration... Let me Know! DrBob. will just attempt to answer some of you questions... You are right, that Bootstrapping the connections is one of the big problems that retroshare faces. The concept of using DHT for finding your buddies sounds like it might work, and enable easy Ip discovery before the conections are made. As to your points about sharing Buddy-Lists.... (1) The Names appear as a long list of *potential peers*, and are not associated with you directly. So if they choose silly names, it shouldn't be a real problem. (2) about Bad Nodes finding out your IP Address. This is only a problem if they can see what you are communicating. As nothing is forwarded over buddies, and everything is encrypted. This is not a problem in RetroShare. :-) > Wrong ? you swarm a file from all your buddies sharing this file and for > searches the same, as well we ned hostbrowsing of buddies, to find new media.. Furthermore: Add a hashsystem to retroshare a) for sharing and for hashlinks, best would be to use the emule hash system. So here is the key, why gaim filesharing plugin makes no sense.... all buddies are peers if they can be swarmed.. this means with swarming in a buddylist and without non-direct transfers we have a normal gnutella style: -> you see for each downloadscheduled file all ip adresses of the sharing buddies. This is, why retroshare is not even private. < PGP Keys: This is a RSA Key + Name, that it is signed by your friends, to say that the key belongs to you. Each person uses their friends signatures to check whether they can trust any new people. look it up in wikipedia... Like your experience with Cspace, most people are offline with RetroShare, I'm working on ideas to make this less of a problem. (Caching + Messages and Channels). Remember Skype and IM work really well, and both people need to be online at the same time there! > Skype has offline Messages, you do not need to bo online, if both buddies are > online again, they transfer (or better exchange later) the messages. Was > suggested for CSpace. < If cspace is interested in collaborating, I would also be interested. but not sure how it integrate C++ and Python..., DrBob. > Ask Sreeram and Jeethu from Tachion or they answer to your mailadress as they > read the messages here. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer _______________________________________________ cspace-users mailing list cspace-users@tachyon.in http://tachyon.in/cgi-bin/mailman/listinfo/cspace-users
