Mercurial > hg > anonet-resdb

comparison doc/www.anonet2.org/public_pod/index.pod @ 516:7e3e97f5442b draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
updated a2.o/index
author Nick <nick@somerandomnick.ano>
date Sun, 05 Jun 2011 12:15:14 +0000
parents 14e9ee532c52
children 235a193fdbef
comparison
equal deleted inserted replaced
515:a29e72c5408d 516:7e3e97f5442b
209 advice here. In addition, the AnoNet2 infrastructure is easy to reuse 209 advice here. In addition, the AnoNet2 infrastructure is easy to reuse
210 for any other darknet, by design. (Technical ease of forking is a core 210 for any other darknet, by design. (Technical ease of forking is a core
211 goal of AnoNet2. We avoid forks only by being good enough so nobody 211 goal of AnoNet2. We avoid forks only by being good enough so nobody
212 feels the need to fork AnoNet2.) 212 feels the need to fork AnoNet2.)
213 213
214 Finally, you may be getting a bit nervous at the amount of regulation 214 Finally, L<you may be getting a bit nervous at the
215 piling up around the world against the public Internet. Since the 215 amount of regulation piling up around the world against the public
216 "public" Internet is owned and managed by a number of multinational 216 Internet|http://www.telegraph.co.uk/technology/news/8481330/Alarm-over-EU-Great-Firewall-proposal.html>.
217 corporations, it's fairly easy for governments to regulate it. Part of 217 Since the "public" Internet is owned and managed by a number of
218 the main purpose behind AnoNet has always been to get away from those 218 multinational corporations, it's fairly easy for governments to regulate
219 private control points, in order to create a truly public internet. 219 it. Part of the main purpose behind AnoNet has always been to get away
220 In AnoNet1, anybody who can regulate crzydmnd can regulate AnoNet1's 220 from those private control points, in order to create a truly public
221 "official" wiki (and by extension, its resource "database"), and 221 internet. In AnoNet1, anybody who can regulate crzydmnd can regulate
222 anybody who can regulate Kaos can regulate AnoNet1's "official" client 222 AnoNet1's "official" wiki (and by extension, its resource "database"),
223 port (and by extension, all new AnoNet1 users), so the private control 223 and anybody who can regulate Kaos can regulate AnoNet1's "official"
224 point problem hasn't quite been solved there. AnoNet2 is still largely 224 client port (and by extension, all new AnoNet1 users), so the private
225 controlled by UFO and somerandomnick, but we have both technical and 225 control point problem hasn't quite been solved there. AnoNet2 is still
226 administrative measures in place to ensure that as the network grows, 226 largely controlled by UFO and somerandomnick, but we have both technical
227 and administrative measures in place to ensure that as the network grows,
227 the two of us will no longer have enough control to destroy the network, 228 the two of us will no longer have enough control to destroy the network,
228 even if our own governments ever decide to try regulating us. 229 even if our own governments ever decide to try regulating us.
229 230
230 Here's an interesting exchange: 231 Here's an interesting exchange:
231 232
511 case of hardware/software failures without dropping messages and without 512 case of hardware/software failures without dropping messages and without
512 duplicating messages, and avoids the long relay chains that normally 513 duplicating messages, and avoids the long relay chains that normally
513 take up half your screen. 514 take up half your screen.
514 515
515 Update: SRN implemented udpmsg4 (a modification to udpmsg3 to 516 Update: SRN implemented udpmsg4 (a modification to udpmsg3 to
516 support binary data without escaping, and to reduce code size and CPU 517 support binary data without escaping, and to reduce code size and
517 cycles to read and write the protocol), and SRN and sevilNatas now 518 CPU cycles to read and write the protocol), and a few users now
518 have IRC servers connecting to the udpmsg4 cloud (running L<SRN's new 519 have IRC servers connecting to the udpmsg4 cloud (running L<SRN's new
519 IRCd|http://www.powerfulproxy.com/do_it.php/http/www.srw.ano/udpmsg4ircd>). 520 IRCd|http://www.powerfulproxy.com/do_it.php/http/www.srw.ano/udpmsg4ircd>).
520 SRN also runs a udpmsg3 bridge. 521 SRN and sevilNatas also run udpmsg3 bridges.
521 522
522 =item Outbound HTTP Proxies 523 =item Outbound HTTP Proxies
523 524
524 SRN runs three right now and ryuk runs one, but that means between the 525 SRN runs three right now and ryuk runs one, but that means between the
525 two of them they can snoop on all HTTP traffic from AnoNet2 to IcannNet. 526 two of them they can snoop on all HTTP traffic from AnoNet2 to IcannNet.