Changes between Initial Version and Version 1 of org/meetings/2019Stockholm/Notes/GrowingTheTorNetwork

Jul 13, 2019, 1:16:43 PM (6 months ago)



  • org/meetings/2019Stockholm/Notes/GrowingTheTorNetwork

    v1 v1  
     1Growing the Tor Network
     4goal: add more relays and more capacity.
     5companies approach and want to help but fear breaking the network
     6cost is inconsequential but want guidelines to follow in a blog post
     81. publish guidelines for large companies + pr + relationship management
     92. donations to existing orgs
     103. relay campaigns (kill its)
     114. Expensive dev
     13What are the failure modes/risks/recommendations to include in that messaging?
     14- 10% of the network is the limit. If you want to run more, consider donating to existing orgs running relays.
     15- Exits take more consideration, see the relay guide
     16- If you cannot run yourself, you can contact an existing org. (We need to update our list. We may need to do a call for updating this list.)
     17- Diversity (but capacity priority). 95% bridges are Linux. Relays are 90%.
     18- Encourage your partner orgs
     19- Myth that if you run an exit, you shouldn’t run a bridge and vice versa. Doesn’t matter who runs bridges. Participation is more important.
     20- Frame guidelines as must have and nice to have.
     21- Nice: diversity. Do what you are most comfortable with.
     22- Provisioning. More info on torservers wiki page.
     23- Maintenance: Recommend making a fellow position. Grow the ISPs that can give for free. If you’re going to give us X, where is best spent?
     24- Someone should be monitoring the relays
     25- Use the back port version or our repos
     28Imagine someone wants to put in 300k for capacity. They should spend the first bit running on their own then donating to an org. Then pay a fellow to be the org advocacy person.
     30Make sure that relay guide / community portal includes recommendations to update the tor version, use latest version. Will ask people who maintain deb package if they can update it more or shift responsibility. Problem for deb stable is a policy issue not to accept new feature changes. But there can be a back port, other workarounds. Acute can make a back port
     32A lot of the work is people growing and maintaining the relationships
     35We need to update:
     36- partner/existing org list
     37- specifications (currently being moved to community portal) can be updated in git
     40Pitch / benefits:
     41Consider the bandwidth you use and then multiply, overestimate, make sure you are giving back. A commons. Benefit human rights — being part of the internet freedom community. Free speech supporter, opposing censorship. Consider the mission or current campaign of each company we’re approaching. Frame in their language.
     43Gamification proposal for relay listings
     44Relay search currently shows individual relays — how can we show relay teams?
     46Do we have any legal support to include in communications?
     47- EFF has a Tor legal FAQ. It was last updated in 2014. Ask about updating. Can we coordinate a campaign with them?
     49What organizations / companies should we go to?
     50There is a fundraising initiative to contact a list of companies, but it would likely be different people making decisions.
     51Should we have separate outreach to companies outside the US? We have strong partnerships related to Torservers.
     52Look for orgs that have it in their mission. Look for companies that have technical people and extra bandwidth.
     53Approach VPN companies. Companies who have onion addresses but not relays.
     54Universities. Can be hard to get university to run because it is like a business and what is the value?
     56Relay Campaigns (Kill LTS!)
     57- should we consider what other campaigns are running alongside?
     58- Run in September? Ask EFF to amplify or run their own.
     59- September also a campaign to run bridges.
     60- Who else could help? CCC, Bits of Freedom. Can we prepare them to push to constituents
     61- Need to get debian relays not to run LTS. Just use app sources. Some cannot switch. Part of relay coordinator role
     62- Campaign to get people to update. Then start putting loglines into the 029. Give people a shirt once they upgrade
     64Tor maintains list of relays
     65Sometimes relay operators put contact info in their configuration, but not required
     66EFF asked them to prove that people run relay by adding something to relay info
     67There are thousands of people on the tor relays list - most of top 10 relays do not have contact info
     68People who run relays don’t add emails because of spam
     70Next steps:
     71- Recommendations
     72- Update documentation
     73- End of August for blog post, visuals. Components: pitch and company guidelines, matching (if applicable), promote support to existing orgs
     74- List of companies
     75- Promote existing companies, update list
     76- Ask company to match donations campaigns to relay operators? with running own relays? Check internal contacts, each out
     77- Promote companies running relays after
     78-  How can we visualize the impact of the campaign in real time? Build a dashboard on network health
     79- Steph to create timeline, discuss in next comms meeting
     81Side notes
     82Could all relays be a bridge?
     83Diversity important if there are exploits.