get rid of the redundant "after it's working" sections of the two relay pages
Roger Dingledine

Roger Dingledine commited on 2014-06-05 22:03:14
Zeige 2 geänderte Dateien mit 22 Einfügungen und 48 Löschungen.

... ...
@@ -184,55 +184,16 @@ href="<page docs/faq>#RelayOrBridge">non-public bridge</a>.</li><br />
184 184
     <h2><a class="anchor" href="#after">Once your relay is working</a></h2>
185 185
     <br>
186 186
 
187
-    <p>Subscribe to the <a
188
-    href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-announce">tor-announce</a>
189
-    mailing list. It is very low volume, and it will keep you informed
190
-    of new stable releases.</p>
191
-
192
-    <p>As a relay operator, you should consider subscribing to the
193
-    <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">
194
-    tor-relays mailing list</a>. You might find <a
195
-    href="<page docs/documentation>#MailingLists">other higher-volume
196
-    Tor lists</a> of interest to you as well.
187
+    <p>To learn more about the proper care and feeding for your relay,
188
+    see the advice on the <a href=<page docs/tor-relay-debian>#after>Tor
189
+    relay on Debian/Ubuntu</a> page.
197 190
     </p>
198 191
 
199
-    <p><a href="https://weather.torproject.org/">Tor Weather</a> provides
200
-    an email notification service to any users who want to monitor the
201
-    status of a Tor node. Upon subscribing, you can specify what types of
202
-    alerts you would like to receive. The main purpose of Tor Weather is
203
-    to notify node operators via email if their node is down for longer
204
-    than a specified period, but other notification types are available.
205
-    </p>
206
-
207
-    <p>Read
208
-    <a href="<wiki>doc/OperationalSecurity">about operational security</a>
209
-    to get ideas how you can increase the security of your relay.
210
-    </p>
211
-
212
-    <p>
213
-    If you control the name servers for your domain, consider setting your
214
-    reverse DNS hostname to 'anonymous-relay', 'proxy' or 'tor-proxy', so when
215
-    other people see the address in their web logs, they will more quickly
216
-    understand what's going on. Adding the <a
217
-    href="<gitblob>contrib/operator-tools/tor-exit-notice.html">Tor
218
-    exit notice</a> on a vhost for this name can go a long way to deterring abuse
219
-    complaints to you and your ISP if you are running an exit node.
220
-    </p>
221
-
222
-    <p>
223
-    When you change your Tor configuration, remember to verify that your
224
-    relay still works correctly after the change.
225
-    If you have problems or questions, see
226
-    the <a href="<page docs/documentation>#Support">Support</a> section or
227
-    <a href="<page about/contact>">contact us</a>. Thanks
228
-    for helping to make the Tor network grow!
229
-    </p>
230
-
231
-
232 192
     <hr>
233 193
 
234 194
     <p>If you have suggestions for improving this document, please <a
235
-    href="<page about/contact>">send them to us</a>. Thanks!</p>
195
+    href="<page about/contact>">send them to us</a>. Thanks
196
+    for helping to make the Tor network grow!</p>
236 197
   </div>
237 198
   <!-- END MAINCOL -->
238 199
   <div id = "sidecol">
... ...
@@ -131,16 +131,24 @@ href="<wiki>/doc/TorExitGuidelines">guidelines
131 131
     </p>
132 132
 
133 133
     <p>
134
-    9. If you run an exit relay (great!), don't miss out on our <a href="<wiki>doc/TorExitGuidelines">Exit Guidelines</a>.
134
+    9. If you run an exit relay (great!), don't miss out on our <a
135
+    href="<wiki>doc/TorExitGuidelines">Exit Guidelines</a>, including
136
+    setting your reverse DNS hostname to make it obvious that you're
137
+    a Tor exit relay, and serving the <a
138
+    href="<gitblob>contrib/operator-tools/tor-exit-notice.html">Tor
139
+    exit notice</a> page on your DirPort.
135 140
     </p>
136 141
 
137 142
     <p>
138 143
     10. Subscribe to the <a
139 144
     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-announce">tor-announce</a>
140 145
     mailing list. It is very low volume, and it will keep you informed
141
-    of new stable releases. You might also consider subscribing to <a
142
-    href="<page docs/documentation>#MailingLists">the higher-volume Tor lists</a>
143
-    too (especially tor-relays).
146
+    of new stable releases.
147
+    As a relay operator, you should consider subscribing to the
148
+    <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">
149
+    tor-relays mailing list</a> too.
150
+    We have more <a href="<page docs/documentation>#MailingLists">mailing
151
+    lists</a> as well.
144 152
     </p>
145 153
 
146 154
     <p>
... ...
@@ -175,6 +183,11 @@ href="<wiki>/doc/TorExitGuidelines">guidelines
175 183
     in (so your user is actually in the group), and run "arm".
176 184
     </p>
177 185
 
186
+    <p>
187
+    15. When you change your Tor configuration, remember to verify that
188
+    your relay still works correctly after the change.
189
+    </p>
190
+
178 191
     <hr>
179 192
 
180 193
     <p>If you have suggestions for improving this document, please <a
181 194