Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #31993

Closed (moved)
Open
Opened Oct 08, 2019 by Trac@tracbot

Remove /doc/GoodBadISPs

This list of ISPs is misleading and in worst case prevents other users from setting up a relay because they might read an old statement which is maybe even influenced by only one specific case.

For example one ISP (Webtropia.com - AS24961) with a consensus weight of 2,15% is listed that they do not tolerate any Tor nodes. When i talked with them about my relay which i set up there before i found that list they answered that they know what Tor is but didnt knew that there are relays running in their network and that running a relay in their network of course is no problem for them.

I think it is pretty depending on the support person you talk to which answer you get. Even if a provider had an internal decision about running Tor relays that decision can change daily so i think properly maintaining that list is not possible. I think that list the way it is now is more harming the expansion and diversity of Tor than helping.

Maybe a hint for the operator to closely read the TOS of the provider would be more helpful. If a provider dont like Tor relays in his network they usually clearly exclude them in their TOS. If they dont exclude them in the worst case they will shut it down.

Trac:
Username: computer_freak

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#31993