#24497: Improve documentation for tor relay operators ------------------------------+------------------------ Reporter: arthuredelstein | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: Component: Webpages/Website | Version: Severity: Normal | Resolution: Keywords: ux-team | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ------------------------------+------------------------
Comment (by cypherpunks): Replying to [comment:32 alison]: > I migrated everything from our original post. Some things to note: > > * My original plan to move away from all externally linked content has not happened. Lots of the links have images and additional links, so I couldn't easily create new trac pages. So maybe we should do that part more gradually. > * I have not migrated the iptables rules because there is a conversation happening on the pad about them. The pad is probably not suitable for discussions, lets use tor-dev@ or discuss directly here on the trac ticket (I'd prefer email over a website). Points I'd like mention here so people can say something if they disagree: * target audience of the guide: people that do not fear the command line and have some minimal Linux or BSD experience * target servers: * the guide should work for servers not exclusively used for Tor, so if someone has a webserver with lots of bw and wants to help, this guide should work for them * for exit relays this is a very different matter: In my opinion you should NOT run an exit relay on a shared server (although I'm aware that a big operator does) - this (exclusive servers for exits) will be clearly stated in the guide. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24497#comment:33> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs