hsribei · January 18, 2017 22:08 · Jul 11, 2014 · Jul 11, 2014 · Jul 11, 2014 · Jul 11, 2014
diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -32,7 +32,7 @@ Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwi
 
 **The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad, in fact, that it takes up most of the Internet's traffic) in exchange for relaying traffic for the rest of the Tor network.**
 
-To boot, you end up with a very, very private torrent network that never touches exit nodes.
+As a bonus, you end up with a very, very private torrent network that never touches exit nodes.
 
 ## You'll _still_ break the network!
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -1,7 +1,7 @@
 ## Putting the "Tor" back in Torrent
 #### How a Popcorn Time ~~fork~~ [patch](https://twitter.com/xaiki/status/487732035331842048) could incentivize people to run thousands of new Tor relays
 
-This is a follow-up to this discussion: [Can NAT traversal be Tor's killer feature?](https://news.ycombinator.com/item?id=8018213)
+*This is a follow-up to this discussion: [Can NAT traversal be Tor's killer feature?](https://news.ycombinator.com/item?id=8018213)*
 
 **If torrents are P2P's killer application, and NAT traversal/"static IP" are Tor's (via hidden services), putting them together could prove to be the best incentivization scheme for growing the Tor network other than [cold crypto cash](http://www.cryptocoinsnews.com/news/torcoin-making-anonymity-pay/2014/06/06).**
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -1,7 +1,7 @@
 ## Putting the "Tor" back in Torrent
 #### How a Popcorn Time ~~fork~~ [patch](https://twitter.com/xaiki/status/487732035331842048) could incentivize people to run thousands of new Tor relays
 
-Thinking about NAT traversal as Tor's killer feature lead to this discussion: https://news.ycombinator.com/item?id=8018213
+This is a follow-up to this discussion: [Can NAT traversal be Tor's killer feature?](https://news.ycombinator.com/item?id=8018213)
 
 **If torrents are P2P's killer application, and NAT traversal/"static IP" are Tor's (via hidden services), putting them together could prove to be the best incentivization scheme for growing the Tor network other than [cold crypto cash](http://www.cryptocoinsnews.com/news/torcoin-making-anonymity-pay/2014/06/06).**
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -1,5 +1,5 @@
 ## Putting the "Tor" back in Torrent
-#### How a Popcorn Time fork could incentivize people to run thousands of new Tor relays
+#### How a Popcorn Time ~~fork~~ [patch](https://twitter.com/xaiki/status/487732035331842048) could incentivize people to run thousands of new Tor relays
 
 Thinking about NAT traversal as Tor's killer feature lead to this discussion: https://news.ycombinator.com/item?id=8018213
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -50,6 +50,10 @@ Oh, and for every 100 new relays, you gain on average X extra kbytes
 of download speed: help us get to this month's goal of another 100 by
 donating 5 bucks a month!
 
+## Credits
+
+All of this was inspired by Ricochet IM (https://ricochet.im), a hidden-services-based, serverless anonymous chat app by the great @special. You should try it out! I'm (among others) `ricochet:2xfy7pfetq2ueyff`.
+
 ## What do you say?
 
 Alright, now back to me being stupid, please tear this idea down :) Thanks!

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -39,7 +39,7 @@ To boot, you end up with a very, very private torrent network that never touches
 Even if these torrent nodes are a net positive in terms of relay capacity, this much usage of hidden services would probably put an unanticipated load on hidden service directories and introduction points. That could turn out to be a problem.
 
 With enough demand, though, I think capacity finds a way
-of taking care of itself. Isn't "the whole Internet is all of a sudden trying to get private!" the thing we want the most? Much better problem trying to scale a network that a lot of people want to use, than trying to convince people to use something they don't see a need for.
+of taking care of itself. Isn't "the whole Internet is all of a sudden trying to get private!" the thing we want the most? **Much better problem trying to scale a network that a lot of people want to use, than trying to convince people to use something they don't see a need for.**
 
 If it's something people want, they'll find
 out about "how to make X faster" and learn that it's based on Tor and

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -52,6 +52,13 @@ donating 5 bucks a month!
 
 ## What do you say?
 
-Alright, now back to me being stupid, please tear this idea down :)
+Alright, now back to me being stupid, please tear this idea down :) Thanks!
 
-<small>*: There's an issue with running a relay and a hiddens service on the same machine. Discussion here: https://lists.torproject.org/pipermail/tor-talk/2014-July/033819.html</small>
+Cheers,
+Helder
+
+<small>*: There's an issue with running a relay and a hiddens service on the same machine. Discussion here: https://lists.torproject.org/pipermail/tor-talk/2014-July/033819.html</small>
+
+P.S.: you can follow me [@obvio171](https://twitter.com/obvio171) on Twitter.
+
+P.S.2: comments on Hacker News: https://news.ycombinator.com/item?id=8022341.
diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -30,7 +30,7 @@ This "Onion Popcorn" could also **_soft-enforce_ download limits** based on the
 
 Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwise should work for downloading and watching.
 
-**The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad, in fact, that it takes up most of the Internet's traffic).**
+**The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad, in fact, that it takes up most of the Internet's traffic) in exchange for relaying traffic for the rest of the Tor network.**
 
 To boot, you end up with a very, very private torrent network that never touches exit nodes.
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -19,7 +19,7 @@ Say we do the following:
 2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT to fetch peers;
 3. Connect to peers via their hidden services.
 
-## You'll break the network!
+## Stop righ there, you'll break the network!
 
 Oh, I forgot:
 4. Make the Popcorn Time fork also **be a relay by default\* whenever possible**.

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -9,7 +9,7 @@ Thinking about NAT traversal as Tor's killer feature lead to this discussion: ht
 
 Everybody knows [you're not supposed to use torrents with tor](https://blog.torproject.org/blog/bittorrent-over-tor-isnt-good-idea), right?
 
-But the problem there is using _existing_ bittorent clients and how they leak IPs to trackers, etc. Drop those stones for a second and hear me out.
+But the problem there is using _existing_ bittorent clients and how they leak IPs to trackers, etc. Drop those stones for a second and hear me out. We're not proxying traffic from regular bittorrent clients through tor, we're making something new.
 
 ## Onion Popcorn
 
@@ -19,7 +19,6 @@ Say we do the following:
 2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT to fetch peers;
 3. Connect to peers via their hidden services.
 
-
 ## You'll break the network!
 
 Oh, I forgot:

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -55,4 +55,4 @@ donating 5 bucks a month!
 
 Alright, now back to me being stupid, please tear this idea down :)
 
-<small>There's an issue with running a relay and a hiddens service on the same machine. Discussion here: https://lists.torproject.org/pipermail/tor-talk/2014-July/033819.html</small>
+<small>*: There's an issue with running a relay and a hiddens service on the same machine. Discussion here: https://lists.torproject.org/pipermail/tor-talk/2014-July/033819.html</small>
diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -31,7 +31,7 @@ This "Onion Popcorn" could also **_soft-enforce_ download limits** based on the
 
 Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwise should work for downloading and watching.
 
-**The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad, in fact, that it takes up most internet traffic).**
+**The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad, in fact, that it takes up most of the Internet's traffic).**
 
 To boot, you end up with a very, very private torrent network that never touches exit nodes.
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -31,7 +31,7 @@ This "Onion Popcorn" could also **_soft-enforce_ download limits** based on the
 
 Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwise should work for downloading and watching.
 
-**The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad that it takes up most internet traffic).**
+**The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad, in fact, that it takes up most internet traffic).**
 
 To boot, you end up with a very, very private torrent network that never touches exit nodes.
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -27,7 +27,7 @@ Oh, I forgot:
 
 Nobody would agree to do this on the main tor software for a thousand reasons, but it's an *app* and you can decide to do that in it independently. If you're going to add a lot of load to the network, you have to give back.
 
-This "Onion Popcorn" could also **_soft-enforce_ download limits** based on the amount of traffic the user has relayed. **Sane defaults and interface nudges can go a long way.** (Popcorn Time itself doesn't even expose network/bandwidth adjustments to the user and, for the mainstream, we can count on hiding some options as an easier alternative to coming up with a proof-of-correctness anti-leeching scheme.)
+This "Onion Popcorn" could also **_soft-enforce_ download limits** based on the amount of traffic the user has relayed. **Sane defaults and interface nudges can go a long way.** (Popcorn Time itself doesn't even expose network/bandwidth adjustments to the user and, for the mainstream, we can count on hiding some options as something easier to do than coming up with a proof-of-correctness anti-leeching scheme.)
 
 Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwise should work for downloading and watching.
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -16,13 +16,14 @@ But the problem there is using _existing_ bittorent clients and how they leak IP
 Say we do the following:
 
 1. Make a DHT that serves out peer onion addresses (OAs?) instead of IP addresses;
-2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT;
+2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT to fetch peers;
+3. Connect to peers via their hidden services.
 
 
 ## You'll break the network!
 
 Oh, I forgot:
-3. Make the Popcorn Time fork also **be a relay by default\* whenever possible**.
+4. Make the Popcorn Time fork also **be a relay by default\* whenever possible**.
 
 Nobody would agree to do this on the main tor software for a thousand reasons, but it's an *app* and you can decide to do that in it independently. If you're going to add a lot of load to the network, you have to give back.
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -22,7 +22,9 @@ Say we do the following:
 ## You'll break the network!
 
 Oh, I forgot:
-3. Make the Popcorn Time fork also be a relay by default\* whenever possible. If you're going to add a lot of load to the network, you have to give back.
+3. Make the Popcorn Time fork also **be a relay by default\* whenever possible**.
+
+Nobody would agree to do this on the main tor software for a thousand reasons, but it's an *app* and you can decide to do that in it independently. If you're going to add a lot of load to the network, you have to give back.
 
 This "Onion Popcorn" could also **_soft-enforce_ download limits** based on the amount of traffic the user has relayed. **Sane defaults and interface nudges can go a long way.** (Popcorn Time itself doesn't even expose network/bandwidth adjustments to the user and, for the mainstream, we can count on hiding some options as an easier alternative to coming up with a proof-of-correctness anti-leeching scheme.)
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -17,6 +17,11 @@ Say we do the following:
 
 1. Make a DHT that serves out peer onion addresses (OAs?) instead of IP addresses;
 2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT;
+
+
+## You'll break the network!
+
+Oh, I forgot:
 3. Make the Popcorn Time fork also be a relay by default\* whenever possible. If you're going to add a lot of load to the network, you have to give back.
 
 This "Onion Popcorn" could also **_soft-enforce_ download limits** based on the amount of traffic the user has relayed. **Sane defaults and interface nudges can go a long way.** (Popcorn Time itself doesn't even expose network/bandwidth adjustments to the user and, for the mainstream, we can count on hiding some options as an easier alternative to coming up with a proof-of-correctness anti-leeching scheme.)
@@ -27,7 +32,7 @@ Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwi
 
 To boot, you end up with a very, very private torrent network that never touches exit nodes.
 
-## You'll break the network!
+## You'll _still_ break the network!
 
 Even if these torrent nodes are a net positive in terms of relay capacity, this much usage of hidden services would probably put an unanticipated load on hidden service directories and introduction points. That could turn out to be a problem.
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -17,7 +17,7 @@ Say we do the following:
 
 1. Make a DHT that serves out peer onion addresses (OAs?) instead of IP addresses;
 2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT;
-3. Make the Popcorn Time fork also be a relay by default\*. If you're going to add a lot of load to the network, you have to give back.
+3. Make the Popcorn Time fork also be a relay by default\* whenever possible. If you're going to add a lot of load to the network, you have to give back.
 
 This "Onion Popcorn" could also **_soft-enforce_ download limits** based on the amount of traffic the user has relayed. **Sane defaults and interface nudges can go a long way.** (Popcorn Time itself doesn't even expose network/bandwidth adjustments to the user and, for the mainstream, we can count on hiding some options as an easier alternative to coming up with a proof-of-correctness anti-leeching scheme.)
 
@@ -27,6 +27,24 @@ Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwi
 
 To boot, you end up with a very, very private torrent network that never touches exit nodes.
 
+## You'll break the network!
+
+Even if these torrent nodes are a net positive in terms of relay capacity, this much usage of hidden services would probably put an unanticipated load on hidden service directories and introduction points. That could turn out to be a problem.
+
+With enough demand, though, I think capacity finds a way
+of taking care of itself. Isn't "the whole Internet is all of a sudden trying to get private!" the thing we want the most? Much better problem trying to scale a network that a lot of people want to use, than trying to convince people to use something they don't see a need for.
+
+If it's something people want, they'll find
+out about "how to make X faster" and learn that it's based on Tor and
+that you should become a relay or donate money here so that your
+connection gets faster.
+
+Oh, and for every 100 new relays, you gain on average X extra kbytes
+of download speed: help us get to this month's goal of another 100 by
+donating 5 bucks a month!
+
+## What do you say?
+
 Alright, now back to me being stupid, please tear this idea down :)
 
 <small>There's an issue with running a relay and a hiddens service on the same machine. Discussion here: https://lists.torproject.org/pipermail/tor-talk/2014-July/033819.html</small>
diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -23,6 +23,10 @@ This "Onion Popcorn" could also **_soft-enforce_ download limits** based on the
 
 Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwise should work for downloading and watching.
 
-The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad that it takes up most internet traffic).
+**The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad that it takes up most internet traffic).**
+
+To boot, you end up with a very, very private torrent network that never touches exit nodes.
+
+Alright, now back to me being stupid, please tear this idea down :)
 
 <small>There's an issue with running a relay and a hiddens service on the same machine. Discussion here: https://lists.torproject.org/pipermail/tor-talk/2014-July/033819.html</small>
diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -19,7 +19,7 @@ Say we do the following:
 2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT;
 3. Make the Popcorn Time fork also be a relay by default\*. If you're going to add a lot of load to the network, you have to give back.
 
-This "Onion Popcorn" could also *soft-enforce* some download limit based on the amount of traffic the user has relayed. Sane defaults and interface nudges can go a long way. (Popcorn Time itself doesn't even expose network/bandwidth adjustments to the user and, for the mainstream, we can count on hiding some options as an easier alternative to coming up with a proof-of-correctness anti-leeching scheme.)
+This "Onion Popcorn" could also **_soft-enforce_ download limits** based on the amount of traffic the user has relayed. **Sane defaults and interface nudges can go a long way.** (Popcorn Time itself doesn't even expose network/bandwidth adjustments to the user and, for the mainstream, we can count on hiding some options as an easier alternative to coming up with a proof-of-correctness anti-leeching scheme.)
 
 Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwise should work for downloading and watching.
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -3,18 +3,26 @@
 
 Thinking about NAT traversal as Tor's killer feature lead to this discussion: https://news.ycombinator.com/item?id=8018213
 
-Here's a related idea that could add a ton of new relays to the Tor network without having to go all "transparent through virtual network interface" right from the start:
+**If torrents are P2P's killer application, and NAT traversal/"static IP" are Tor's (via hidden services), putting them together could prove to be the best incentivization scheme for growing the Tor network other than [cold crypto cash](http://www.cryptocoinsnews.com/news/torcoin-making-anonymity-pay/2014/06/06).**
 
-1. Make a DHT that serves out peer onion addresses (OAs?) instead of IPs;
+## You're stupid
+
+Everybody knows [you're not supposed to use torrents with tor](https://blog.torproject.org/blog/bittorrent-over-tor-isnt-good-idea), right?
+
+But the problem there is using _existing_ bittorent clients and how they leak IPs to trackers, etc. Drop those stones for a second and hear me out.
+
+## Onion Popcorn
+
+Say we do the following:
+
+1. Make a DHT that serves out peer onion addresses (OAs?) instead of IP addresses;
 2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT;
-3. Make the Popcorn Time fork also be a relay by default\*. You'll add a lot of load to the network, so you have to give back.
+3. Make the Popcorn Time fork also be a relay by default\*. If you're going to add a lot of load to the network, you have to give back.
 
-This "Onion Popcorn" could also *soft-enforce* some download limit based on the amount of traffic the user has relayed. Sane defaults and interface nudges can go a long way (Popcorn Time itself doesn't even expose network/bandwidth adjustments to the user).
+This "Onion Popcorn" could also *soft-enforce* some download limit based on the amount of traffic the user has relayed. Sane defaults and interface nudges can go a long way. (Popcorn Time itself doesn't even expose network/bandwidth adjustments to the user and, for the mainstream, we can count on hiding some options as an easier alternative to coming up with a proof-of-correctness anti-leeching scheme.)
 
 Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwise should work for downloading and watching.
 
 The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad that it takes up most internet traffic).
 
-If torrents are P2P's killer application, and NAT traversal/"static IP" Tor's, this could prove to be the best incentivization scheme for growing the Tor network other than [plain cash](http://www.cryptocoinsnews.com/news/torcoin-making-anonymity-pay/2014/06/06). 
-
 <small>There's an issue with running a relay and a hiddens service on the same machine. Discussion here: https://lists.torproject.org/pipermail/tor-talk/2014-July/033819.html</small>
diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -1,5 +1,5 @@
 ## Putting the "Tor" back in Torrent
-#### How Popcorn Time could incentivize people to run thousands of new Tor relays
+#### How a Popcorn Time fork could incentivize people to run thousands of new Tor relays
 
 Thinking about NAT traversal as Tor's killer feature lead to this discussion: https://news.ycombinator.com/item?id=8018213
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -9,8 +9,12 @@ Here's a related idea that could add a ton of new relays to the Tor network with
 2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT;
 3. Make the Popcorn Time fork also be a relay by default\*. You'll add a lot of load to the network, so you have to give back.
 
-This "Popcorn Tor" (too bad can't use the name ;)) could also soft-enforce some download limit based on the amount of traffic the user has relayed. Sane defaults and interface nudges can go a long way.
+This "Onion Popcorn" could also *soft-enforce* some download limit based on the amount of traffic the user has relayed. Sane defaults and interface nudges can go a long way (Popcorn Time itself doesn't even expose network/bandwidth adjustments to the user).
 
 Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwise should work for downloading and watching.
 
+The end result is that you're incentivizing Tor "miners" by giving them something they want (so bad that it takes up most internet traffic).
+
+If torrents are P2P's killer application, and NAT traversal/"static IP" Tor's, this could prove to be the best incentivization scheme for growing the Tor network other than [plain cash](http://www.cryptocoinsnews.com/news/torcoin-making-anonymity-pay/2014/06/06). 
+
 <small>There's an issue with running a relay and a hiddens service on the same machine. Discussion here: https://lists.torproject.org/pipermail/tor-talk/2014-July/033819.html</small>
diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -1,7 +1,7 @@
 ## Putting the "Tor" back in Torrent
 #### How Popcorn Time could incentivize people to run thousands of new Tor relays
 
-Thinking about Tor as NAT traversal lead to this discussion: https://news.ycombinator.com/item?id=8018213
+Thinking about NAT traversal as Tor's killer feature lead to this discussion: https://news.ycombinator.com/item?id=8018213
 
 Here's a related idea that could add a ton of new relays to the Tor network without having to go all "transparent through virtual network interface" right from the start:
 

diff --git a/putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent.md
@@ -1,5 +1,5 @@
 ## Putting the "Tor" back in Torrent
-##### How Popcorn Time could incentivize people to run thousands of new Tor relays
+#### How Popcorn Time could incentivize people to run thousands of new Tor relays
 
 Thinking about Tor as NAT traversal lead to this discussion: https://news.ycombinator.com/item?id=8018213
 

diff --git a/putting-the-tor-back-in-torrent → putting-the-tor-back-in-torrent.md b/putting-the-tor-back-in-torrent → putting-the-tor-back-in-torrent.md
diff --git a/...ple-to-run-thousands-of-new-tor-relays.md → putting-the-tor-back-in-torrent b/...ple-to-run-thousands-of-new-tor-relays.md → putting-the-tor-back-in-torrent
@@ -1,4 +1,5 @@
-# How Popcorn Time could incentivize people to run thousands of new Tor relays
+## Putting the "Tor" back in Torrent
+##### How Popcorn Time could incentivize people to run thousands of new Tor relays
 
 Thinking about Tor as NAT traversal lead to this discussion: https://news.ycombinator.com/item?id=8018213
 

diff --git a/how-popcorn-time-could-incentivize-people-to-run-thousands-of-new-tor-relays.md b/how-popcorn-time-could-incentivize-people-to-run-thousands-of-new-tor-relays.md
@@ -10,6 +10,6 @@ Here's a related idea that could add a ton of new relays to the Tor network with
 
 This "Popcorn Tor" (too bad can't use the name ;)) could also soft-enforce some download limit based on the amount of traffic the user has relayed. Sane defaults and interface nudges can go a long way.
 
-Probably wouldn't be able to _stream_ anything, but otherwise should work.
+Bandwidth at first probably wouldn't be enough to _stream_ anything, but otherwise should work for downloading and watching.
 
 <small>There's an issue with running a relay and a hiddens service on the same machine. Discussion here: https://lists.torproject.org/pipermail/tor-talk/2014-July/033819.html</small>
diff --git a/how-popcorn-time-could-incentivize-people-to-run-thousands-of-new-tor-relays.md b/how-popcorn-time-could-incentivize-people-to-run-thousands-of-new-tor-relays.md
@@ -6,7 +6,7 @@ Here's a related idea that could add a ton of new relays to the Tor network with
 
 1. Make a DHT that serves out peer onion addresses (OAs?) instead of IPs;
 2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT;
-3. Make the Popcorn Time fork also a relay by default\*. You'll add a lot of load to the network, so you have to give back.
+3. Make the Popcorn Time fork also be a relay by default\*. You'll add a lot of load to the network, so you have to give back.
 
 This "Popcorn Tor" (too bad can't use the name ;)) could also soft-enforce some download limit based on the amount of traffic the user has relayed. Sane defaults and interface nudges can go a long way.
 

diff --git a/how-popcorn-time-could-incentivize-people-to-run-thousands-of-new-tor-relays.md b/how-popcorn-time-could-incentivize-people-to-run-thousands-of-new-tor-relays.md
@@ -5,7 +5,7 @@ Thinking about Tor as NAT traversal lead to this discussion: https://news.ycombi
 Here's a related idea that could add a ton of new relays to the Tor network without having to go all "transparent through virtual network interface" right from the start:
 
 1. Make a DHT that serves out peer onion addresses (OAs?) instead of IPs;
-2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA tracker;
+2. Fork Popcorn Time, make it create a hidden service for the user and connect to the OA DHT;
 3. Make the Popcorn Time fork also a relay by default\*. You'll add a lot of load to the network, so you have to give back.
 
 This "Popcorn Tor" (too bad can't use the name ;)) could also soft-enforce some download limit based on the amount of traffic the user has relayed. Sane defaults and interface nudges can go a long way.