I have two proposals to add to the torspec.git. They are:
(1) http://dl.dropbox.com/u/3308162/230-quicken-tor2web-mode.txt (2) http://dl.dropbox.com/u/3308162/231-remittance-addresses.txt
If someone with commit rights will add them that'd be lovely and we can ignore the rest of this message.
If not, I request permission to commit to torspec.git. My PGP is here and we can discuss setting up a password, etc: http://virgil.gr/1+Virgil_Griffith_pub.asc
-V
On 3/27/14, Virgil Griffith i@virgil.gr wrote:
I have two proposals to add to the torspec.git. They are:
(1) http://dl.dropbox.com/u/3308162/230-quicken-tor2web-mode.txt (2) http://dl.dropbox.com/u/3308162/231-remittance-addresses.txt
Hi Virgil,
Upon first peek, I'd say that these proposals aren't quite correctly formatted. Could you format them to fit the line limits and expected text formatting for proposals?
Proposal 230 is very small but it should probably include references to the specs or proposals that you'd expect are impacted by the proposed changes.
Proposal 231 need to be more specific. At the moment it discusses more how a user might use the remittance addresses but nothing about size limits, impact on the network bandwidth, format of the text field, and so on.
I'll be happy to add them once they're formatted slightly more like we'd expect. I think I'd be even happier if they were a little more through too.
All the best, Jake
Virgil Griffith:
I have two proposals to add to the torspec.git. They are:
(1) http://dl.dropbox.com/u/3308162/230-quicken-tor2web-mode.txt (2) http://dl.dropbox.com/u/3308162/231-remittance-addresses.txt
With regard to (2), the torrc file is not a dot file by default. Also the RemittanceAddresses syntax doesn't seem entirely consistent to me. There's also a spelling error in your description. My patch below for (2) addresses these. I don't have any comments for (1).
--- 231-remittance-addresses.txt.orig 2014-03-27 19:27:48.290785904 -0500 +++ 231-remittance-addresses.txt 2014-03-27 19:40:47.107269941 -0500 @@ -5,15 +5,15 @@ Status: Open
Motivation -We wish to add the ability for individual users to donate to the owners of relay operators using a cryptocurrency. We propose adding an optional line to the .torrc file which will be published in the directory consensus and listed on https://compass.torproject.org. +We wish to add the ability for individual users to donate to the owners of relay operators using a cryptocurrency. We propose adding an optional line to the torrc file which will be published in the directory consensus and listed on https://compass.torproject.org.
Proposal
-Allow an optional “RemittanceAddresses” line to the .torrc file containing +Allow an optional “RemittanceAddresses” line to the torrc file containing comma-delimited cryptocurrency URIs. For example,
-RemittanceAddressses bitcoin 19mP9FKrXqL46Si58pHdhGKow88SUPy1V8,namecoin:NAMEuWT2icj3ef8HWJwetZyZbXaZUJ5hFT +RemittanceAddressses bitcoin 19mP9FKrXqL46Si58pHdhGKow88SUPy1V8,namecoin NAMEuWT2icj3ef8HWJwetZyZbXaZUJ5hFT
-The contents of the node’s RemittanceAddresses line will be mirrored in the node’s router descriptor (which is then published in the directory consensus). This line will be treated akin to the ContactInfo field. An address may not contain a colon, coma, or nonprintable ASCII. +The contents of the node’s RemittanceAddresses line will be mirrored in the node’s router descriptor (which is then published in the directory consensus). This line will be treated akin to the ContactInfo field. An address may not contain a colon, comma, or nonprintable ASCII.