Mercurial > hg > anonet-resdb

comparison doc/www.anonet2.org/public_pod/index.pod @ 313:d56e4aa1784e draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
added lex to the udpmsg3 world on a2.o :-)
author Nick <nick@somerandomnick.ano>
date Wed, 15 Dec 2010 01:14:23 +0000
parents 291f1216c340
children b80d37930062
comparison
equal deleted inserted replaced
312:ba07a102d7e9 313:d56e4aa1784e
377 want to deal with this is still a topic for open discussion. Feel free 377 want to deal with this is still a topic for open discussion. Feel free
378 to join in the discussion, or just do your own thing and let everyone 378 to join in the discussion, or just do your own thing and let everyone
379 else be damned.) 379 else be damned.)
380 380
381 Update: UFO implemented udpmsg3 (inspired by r101's udpmsg protocol), 381 Update: UFO implemented udpmsg3 (inspired by r101's udpmsg protocol),
382 and UFO, SRN, and sevilNatas all have IRC servers connecting to the 382 and UFO, SRN, sevilNatas and lex all have IRC servers connecting to the
383 udpmsg3 "cloud" now. The nice thing about udpmsg3 is that it's truly 383 udpmsg3 "cloud" now. The primary advantages of udpmsg3 are that it's
384 decentralized, and very difficult to censor. 384 truly decentralized, very difficult to censor, fails over gracefully in
385 case of hardware/software failures without dropping messages and without
386 duplicating messages, and avoids the long relay chains that normally
387 take up half your screen.
385 388
386 =item Outbound HTTP Proxies 389 =item Outbound HTTP Proxies
387 390
388 SRN runs three right now and ryuk runs one, but that means between the 391 SRN runs three right now and ryuk runs one, but that means between the
389 two of them they can snoop on all HTTP traffic from AnoNet2 to IcannNet. 392 two of them they can snoop on all HTTP traffic from AnoNet2 to IcannNet.