1. ╔══════════════════════════════════════════════════════════════════════════════╗
2. ║                  Peering requirements for cjdns peering.                     ║
3. ║                                                                              ║
4. ║ Clarification of peering requirements for cjdns and the hyperboria testnet.  ║
5. ║                                                                              ║
6. ║ There has been a recent overwhelming increase of interest in this project    ║
7. ║ and a resulting flood of new people trying to find peers.                    ║
8. ║                                                                              ║
9. ║ Please read this entire document and check out the links within PRIOR to     ║
10. ║ asking for a peer.                                                           ║
11. ║                                                                              ║
12. ║ First, please understand this is not a public network and you are not        ║
13. ║ automatically entitled to access it.                                         ║
14. ║                                                                              ║
15. ║ While the final goal is to create a better network where everyone and anyone ║
16. ║ can use it, first we need to build it. This can not be done if we are busy   ║
17. ║ dealing with people and unable to do work on the network. For now we require ║
18. ║ a more strict immigration policy adding on those who can help build up the   ║
19. ║ network and help debug and develop it. For the rest, have patience. We are   ║
20. ║ doing what we can to make a better network for everyone.                     ║
21. ║                                                                              ║
22. ║ This is a private network based on the Friend-of-a-Friend concept. Every     ║
23. ║ node is run by a user who knows someone else, their peers - aka friends.     ║
24. ║ With this linking of friends there is a level of trust beween users.         ║
25. ║                                                                              ║
26. ║ If you need help you can ask your peers. They have been here longer and know ║
27. ║ how things work. Please talk to them prior to asking others, such as the irc ║
28. ║ channels. Feel free to verify if unsure, but try to sort it out on your own  ║
29. ║ first before asking.                                                         ║
30. ║                                                                              ║
31. ║ When you peer to a node it is done (usually) by IPV4/UDP over the existing   ║
32. ║ internet. You trust your peer not to give out your information. At the same  ║
33. ║ time they trust you not to cause any problems on the network. They expect    ║
34. ║ you to be helpful and to contribute to the network and keep your system      ║
35. ║ secure.                                                                      ║
36. ║                                                                              ║
37. ║ This is a test network for alpha software. You must upgrade often to keep    ║
38. ║ current with the protocols as they are developed. Things may break, in fact, ║
39. ║ this will break. This is the nature of the alpha testing stage and the       ║
40. ║ purpose of this test net.                                                    ║
41. ║                                                                              ║
42. ║ This is not a TOR type network. You can not use this to hide your IP or do   ║
43. ║ the inefficent onion random routing. If you want an anoniminity tool, look   ║
44. ║ elsewhere such as I2P or TOR. This network keeps data private, not anon.     ║
45. ║                                                                              ║
46. ║                                                                              ║
47. ║ # Please consider joining the network if...                                  ║
48. ║                                                                              ║
49. ║ -You wish to contribute a vps or dedi peer to the network                    ║
50. ║ We are in need of dedicated hardware on high speed/low latency connections   ║
51. ║ to the internet backbone. These will build up the core of the network so     ║
52. ║ people can find a local node anywhere in the world.                          ║
53. ║                                                                              ║
54. ║ -You have patience                                                           ║
55. ║ This is a very long term project, as in decades, not months. Peering is      ║
56. ║ done by asking around to find someone close then talking to them and         ║
57. ║ asking them to help you get on the network. This is not a fast process.      ║
58. ║ Tell people what you have to offer when asking for peers. It may help.       ║
59. ║                                                                              ║
60. ║ -You have some basic linux skills and understand how to compile a program    ║
61. ║ This tested on Linux (debian or ubuntu) and it is expected you know how      ║
62. ║ to do most common things on your system and can follow directions.           ║
63. ║                                                                              ║
64. ║ -You are in a city and have an interest in setting up a Mesh-Local           ║
65. ║ If you wish to start a mesh-local we can help. Note cjdns itself does not    ║
66. ║ understand wifi or radio packets. Mesh-Locals are 'uses' of cjdns and        ║
67. ║ not directly supported by cjdns coders. Many people do have knowledge on     ║
68. ║ how to do this so ask them on IRC such as #projectmeshnet.                   ║
69. ║                                                                              ║
70. ║ -You can help debug the code                                                 ║
71. ║ If you love coding then we would love to hear from you. The core is          ║
72. ║ written in C99 (cjdns itself). Other languages can be used to access         ║
73. ║ the admin port. There is also a need for anyone who wants to do some         ║
74. ║ kind of service or help diagnose how the network is doing.                   ║
75. ║                                                                              ║
76. ║-You can help debug other ppls code                                           ║
77. ║ Even if you are not an expert coder you could help by running other people's ║
78. ║ code and seeing if it works on your setup. A minimal understanding is needed ║
79. ║ to know if it is your issue or an actual bug in the code.                    ║
80. ║                                                                              ║
81. ║ -You wish to build better community along with a better network              ║
82. ║ We are building a replacement for the internet but we also want to make some ║
83. ║ changes on how the network is utilized. We beleive it should be the users of ║
84. ║ then network who control it, not a centralized organization or random powers ║
85. ║ who claim ownership over it.                                                 ║
86. ║                                                                              ║
87. ║                                                                              ║
88. ║ # Please do not bother the network if..                                      ║
89. ║                                                                              ║
90. ║ -You have a windows machine and no access to a linux box/vps/dedi server     ║
91. ║ You need Linux, OSX, BSD, or something that can compile code.                ║
92. ║ Windows support is in the works but will not be finished until we have more  ║
93. ║ of a core network in place.                                                  ║
94. ║                                                                              ║
95. ║ -You have a dynamic IP on a home internet connection and no vps/dedi server  ║
96. ║ Dynamic and Home networks do not make good peers. They vary in speed as the  ║
97. ║ user does bittorrent or steams video. The ISP filters and limits packets     ║
98. ║ and who knows what else. Connecting from your home node to your VPS or DEDI  ║
99. ║ Server makes sense, connecting a bunch of home systems over ipv4/udp does    ║
100. ║ not.                                                                         ║
101. ║                                                                              ║
102. ║ -You expect it to just work and have no interest in helping developers       ║
103. ║ It will break, it is alpha. The purpose of using this right now is to help   ║
104. ║ build it up, to test it, to make it better.                                  ║
105. ║                                                                              ║
106. ║ -You think this will make you anonymous -> it won't.                         ║
107. ║ Your peers know who you are. They wont keep you as a peer if it means they   ║
108. ║ get depeered for doing so. Do not do things or behave in a manner contrary   ║
109. ║ to what the general community beleives in. Tolerance is expected but there   ║
110. ║ are ofc things that will not be tolerated.                                   ║
111. ║                                                                              ║
112. ║ -You think you should be able to do anything without consequences            ║
113. ║ Not true. See Above                                                          ║
114. ║                                                                              ║
115. ║ -You think public peers are a good thing                                     ║
116. ║ See Above                                                                    ║
117. ║ Also; pub peers will eventually be saturated when enough people find them.   ║
118. ║ This will result in them being very unstable and useless.                    ║
119. ║                                                                              ║
120. ║ -You think our 3 years of work on this project doesn't count                 ║
121. ║ If you think your brilliant idea is so good that we dont have a say in it    ║
122. ║ and we have to impliment it... you are in for a suprise! :)                  ║
123. ║ We have been at this for a long time now and likely have considered it.      ║
124. ║ Ask first, see what was decided. Perhaps it can be modified to work,         ║
125. ║ perhaps not. But accept whatever the final decision is.                      ║
126. ║ If you do not like it, you can always fork off and build your own net.       ║
127. ║                                                                              ║
128. ║ -You think your idea must be done no matter what we tell you otherwise       ║
129. ║ See Above                                                                    ║
130. ║                                                                              ║
131. ║                                                                              ║
132. ║ PEERING                                                                      ║
133. ║                                                                              ║
134. ║ -Make sure your peers are as local as possible to you.                       ║
135. ║ Distance matters as it increases latency which adds up over multiple hops.   ║
136. ║ Use a distant peer from a server->server if you must but replace it with     ║
137. ║ local peers as you find them.                                                ║
138. ║                                                                              ║
139. ║ -Use unique passwords per peer. Do not share passwords. Peering is based on  ║
140. ║ trust and if you give away passwords you abuse the trust of your peer. A     ║
141. ║ solution is to add the peers info (nick, etc) to the password string.        ║
142. ║                                                                              ║
143. ║ -More is not better. 3-5 peers is good. 30 peers is bad.                     ║
144. ║                                                                              ║
145. ║ -NEVER USE A PUBLIC PEER. These degrade the network and make it centralized. ║
146. ║ Each node can handle many peers, but no node can handle the entire internet. ║
147. ║ As this network grows any public peer will simply become saturated and       ║
148. ║ useless causing issues for the entire network.                               ║
149. ║                                                                              ║
150. ║                                                                              ║
151. ║ FIND A PEER                                                                  ║
152. ║                                                                              ║
153. ║ Currently we are using IRC for peering introductions and for general         ║
154. ║ discussions. All users should try to be on IRC to keep up with development   ║
155. ║ and to participate with the community. Things change fast and you will need  ║
156. ║ to keep up to date of developments. Also check out irc.hypeirc.net when on.  ║
157. ║                                                                              ║
158. ║ Come say hi on EFNet:                                                        ║
159. ║  IRC Client: irc://irc.efnet.org/#cjdns (better choice)                      ║
160. ║  Webchat: http://chat.efnet.org:9090/?channels=#cjdns (if no irc client)     ║
161. ║                                                                              ║
162. ║ When asking for peering indicate where your node is (city) and type of peer  ║
163. ║ (home node/vps/dedicated server). See top of this page for suggesions.       ║
164. ║                                                                              ║
165. ║ Have patience as people may be sleeping or otherwise AFK.                    ║
166. ║                                                                              ║
167. ║                                                                              ║
168. ║                                                                              ║
169. ║ Further reading:                                                             ║
170. ║   https://github.com/cjdelisle/cjdns/blob/master/README.md                   ║
171. ║   https://github.com/cjdelisle/cjdns/blob/master/doc/Whitepaper.md           ║
172. ║                                                                              ║
173. ║                                                                              ║
174. ║                                                                              ║
175. ║                                                            ircerr / 20130909 ║
176. ╚══════════════════════════════════════════════════════════════════════════════╝
177.  
178.  
179. #EOF#