<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 7, 2010, at 6:35 PM, Reza Lotun wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Bitstream Vera Sans Mono'; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="font-family: monospace; ">Here's one of many solutions: get one or more publicly available<br>servers, and stick some XMPP software (twisted.words, Punjab,<br>ejabberd, whatever). Turn on SSL. Now you have a secure, centralized<br>communications system.<br></span></span></blockquote></div><br><div>Another solution, if you want to go down the "real P2P" route, is to start maintaining Divmod Vertex <<a href="http://divmod.org/trac/wiki/DivmodVertex">http://divmod.org/trac/wiki/DivmodVertex</a>> - it's a pretty good proof of concept, and solves many of the really hard problems (especially NAT traversal), but it will definitely need to be fixed up if you want to deploy it in a real-world application.</div><div><br></div></body></html>