Tor Operators Community

This community is a dedicated Signal group for medium to large-scale Tor operators to connect, collaborate, and navigate the unique challenges and opportunities that come with running Tor at scale.

While the public IRC/Element channel #tor-relays by the Tor Project serves as an excellent resource for all operators, larger operators often face distinct technical hurdles, legal complexities and operational considerations that benefit from more focused discussion. This community aims to provide a private and efficient platform for us to:

• Share insights, troubleshoot technical issues and challenges, and collaborate on best practices for maintaining and optimizing your Tor relays.
• Exchange information and experiences regarding legal frameworks, compliance, and potential risks associated with operating Tor infrastructure at scale.
• Explore new ways to enhance the Tor network’s robustness and reach, and discuss potential advancements or collaborations.
• Learn from your peers and contribute your own valuable expertise to a community facing similar situations.

We encourage open and respectful dialogue, fostering a supportive environment where operators can freely exchange information and build stronger connections within the Tor ecosystem. Please review the rules and requirements below to ensure a productive and secure experience for everyone.

1 Rules

We’re all here because we are serious about running Tor relays. To actually get things done and to be effective, there are some ground rules to follow. These can be summarized as “don’t be an asshole, keep it private and stick to the point”.

Purpose and scope

1. This community is specifically for medium to large-scale Tor operators and the unique technical and legal challenges they face.
2. Discussions should focus on the challenges, opportunities and operational aspects unique to medium to large-scale Tor operators.
3. General Tor (Browser) usage questions or issues best addressed in public forums (like the Tor Project’s IRC/element channels or forums) should be avoided.
4. Keep discussions relevant to the community’s purpose. Off-topic conversations should be moved to private chats.
5. English is the primary language for all discussions and conversations. This helps ensure the most people can participate and understand the conversation.

Be professional

6. Treat all members with respect and professionalism, especially when opinions differ.
7. Personal attacks, insults, harassment, hate speech or discriminatory language are prohibited.

Privacy & confidentiality

8. Exercise caution when sharing information outside the community. When in doubt, assume it’s confidential.
9. Do not share personal or sensitive (operational) information learned in this community without explicit permission from the source.
10. Be open and transparent about which relay family you operate inside the community. This ensures everyone knows which operator they are interacting with.

No solicitation or self-promotion

11. This group and its members are not to be used for commercial solicitation, advertising, or self-promotion.

2 Operator requirements

To ensure this group is distinct and effective, there are specific criteria for membership, differentiating us from general channels like #tor-relays. Please review these requirements before applying:

1. Your Tor relay family includes at least 25 guard and/or exit relays. Exceptions may be considered for families with exceptionally high bandwidth, even if they have fewer than 25 relays.
2. Your Tor relay family consistently provides at least 4 Gb/s of advertised guard and/or exit bandwidth. Exceptions to this bandwidth requirement may be considered for relays in specific geographic areas known to be disproportionately disadvantaged by the Tor network (e.g. East Asia or the western US).
3. You must be an individual directly managing the Tor relays at a technical level.
4. You have met the above four criteria for a minimum of three months.
5. You are not directly affiliated with the Tor Project.
6. You and/or your organization operates on a non-commercial and non-profit basis. Exceptions to this rule are evaluated individually.
7. A maximum of three individuals per Tor family may join.
8. You commit and adhere to all rules outlined in this document. These rules only apply within this community.

Operators who meet these requirements are encouraged to apply for group membership. Failure to adhere to these requirements can result in removal from the community.

3 Verification process

To maintain the security, relevance and privacy of this group, all prospective group members must complete a verification process. We understand that some operators prefer not to link their real-world identity to their Tor operations, and that physical verification often is unpractical or (financially) unfeasible. Instead the verification process focuses on verifying ownership and/or control over the infrastructure, domain name, website, and phone number used for Signal.

This way we strike a balance between accessibility and identity assurance. While this approach may not align with every operator’s preferences, imposing overly stringent entry/verification requirements would hinder participation and diminish the group’s overall impact, effectiveness and value.

Process

1. You can apply by sending sending us an email.
2. A community administrator will contact you for starting the verification process.
3. The following will be verified:
   • Your commitment to adhering to the rules outlined in this document.
   • Whether your Tor family and you meet the requirements outlined in this document.
   • Ownership and control of the primary domain name/website used for the Tor relay family.
   • The Signal Safety Number.
4. After verification is finished, a community administrator will invite you to the Signal group.

If you have any questions regarding this community, feel free to contact us.