1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zgenjix@yahoo.com>) id 1RbcXR-00082H-Rj
for bitcoin-development@lists.sourceforge.net;
Fri, 16 Dec 2011 18:29:45 +0000
X-ACL-Warn:
Received: from nm28-vm1.bullet.mail.ne1.yahoo.com ([98.138.91.35])
by sog-mx-3.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1RbcXP-0000kX-Bp for bitcoin-development@lists.sourceforge.net;
Fri, 16 Dec 2011 18:29:45 +0000
Received: from [98.138.90.48] by nm28.bullet.mail.ne1.yahoo.com with NNFMP;
16 Dec 2011 18:29:37 -0000
Received: from [98.138.88.232] by tm1.bullet.mail.ne1.yahoo.com with NNFMP;
16 Dec 2011 18:29:37 -0000
Received: from [127.0.0.1] by omp1032.mail.ne1.yahoo.com with NNFMP;
16 Dec 2011 18:29:37 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 920881.91341.bm@omp1032.mail.ne1.yahoo.com
Received: (qmail 25136 invoked by uid 60001); 16 Dec 2011 18:29:37 -0000
X-YMail-OSG: JJn9qEcVM1ngSHWIXxavvMUBVysYCNiKqo0cRPWLKLiIYc7
cL5dkYL9L_1ZLnNHgN9sNP7nuAbkmbkeWaXFzq_o3tn2Eoqyd.BbmprnXBHU
hYFMlbpz.ijYCm_7KGG5OSTua74UJcnt4sCs0jFEa5K_JPxrTGFMoO9IDvUY
5trGVQUK.Qi.KZ6YEaWUePE5I1NA5aGAHlJOhcmGxDySsFeLQoo5qSFibgub
Ioh9Bq8hsQw2xGCjtseud6Q6DvXtSdb1.GRcu5KIn1Wto1RAiYOF6vJyO9wg
S11GKEqA_jQHoy7C5E_MsjZXxMhc6y7pBQL81OBBKacT4AXKNn7YBJMCn7NL
8WWsoVl7Oqj5hzJ7qrIzsN.1.vj3NvqTcwTamhFjeKk_cZGhwkh7r0W0e9_5
r40r8fRbcTCixBvhlfij6GDk_Ws7UA_YKkehOASf41yra6I9TXcv8gNr2tRf
JDLdkvGuAldY-
Received: from [2.97.168.202] by web121006.mail.ne1.yahoo.com via HTTP;
Fri, 16 Dec 2011 10:29:37 PST
X-Mailer: YahooMailWebService/0.8.115.331698
References: <1323731781.42953.YahooMailClassic@web120920.mail.ne1.yahoo.com>
<CAJna-HiR0qrOp2sG0hb=5bJ2H60y7QwC8BiHDVR9=kiV20W0vA@mail.gmail.com>
<CAJ1JLttMWog=QSLmmM9HiZLQ2UU9sPmwAs2wVQoetW3yjMRPow@mail.gmail.com>
<201112161710.15165.andyparkins@gmail.com>
<CAJ1JLts8JQ2J=DqJTD76gq2KB02ycqqeJjwaDyY2tPX8SJwvVA@mail.gmail.com>
Message-ID: <1324060177.10146.YahooMailNeo@web121006.mail.ne1.yahoo.com>
Date: Fri, 16 Dec 2011 10:29:37 -0800 (PST)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CAJ1JLts8JQ2J=DqJTD76gq2KB02ycqqeJjwaDyY2tPX8SJwvVA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="285087016-1047432035-1324060177=:10146"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zgenjix[at]yahoo.com)
-2.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain 1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
2.8 FREEMAIL_REPLYTO Reply-To/From or Reply-To/body contain different
freemails -1.4 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RbcXP-0000kX-Bp
Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 18:29:45 -0000
--285087016-1047432035-1324060177=:10146
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
You have to be seriously joking to call the bitcoin protocol elegant. A mes=
sage based system over TCP with constantly changing endians that needs to l=
ookup its own IP address on several websites is not elegant. It is function=
ing, not elegant.=0A=0AAlso it is kind of dick to come guns blaring and sta=
rt insulting slush who runs one of the biggest mining pools and is working =
on electrum, and sipa who develops the satoshi bitcoin.=0A=0AKhalahan said:=
=0A=0A> Namecoin is a peer-to-peer generic name/value datastore system=0A=
=0ANamecoin has the same problem as DNS. From the document:=0A=0A"The disad=
vantage of DNS TXT records is that updating a record takes =0Atime. This en=
courages people to not use new addresses per transaction =0Awhich has certa=
in security issues."=0A=0A=0A________________________________=0A From: Rick=
Wesson <rick@support-intelligence.com>=0ATo: Andy Parkins <andyparkins@gma=
il.com> =0ACc: bitcoin-development@lists.sourceforge.net =0ASent: Friday, D=
ecember 16, 2011 5:41 PM=0ASubject: Re: [Bitcoin-development] Fwd: [BIP 15]=
Aliases=0A =0AIts a negative example -- in that the IETF does not specify =
anything=0Ain the PATH part of the URI. The scheme, sure, but not in the pa=
th,=0Athere are many types of URI schemes ( start with RFC 2396 )=0A=0ATher=
e is significant upside to having your own scheme and having apps=0Aunderst=
and how to integrate with it. Frankly, having just one client=0A(I understa=
nd there are more) is an artifact that hinders acceptance=0Aand participati=
on. If you want to go the route of https then=0Aspecifying a scheme is your=
path forward=0A=0AI still believe that it is experience that is leading th=
is thread down=0Athe rat-hole of CGI and HTTP requests. The stuff isn't mag=
ic, it is=0Ajust what you are used to. Review the bitcoin protocol, there i=
s an=0Aelegance there -- not found=A0 in the https schemes proposed thus fa=
r.=0ACGI isn't a protocol, nor does it address usability/identity issues.=
=0A=0AProviding a mapping from user@authority.tld addresses usability and=
=0Aidentity. I'd like to see an elegant transformation, specifically I=0Ata=
ke to task anyone that advocates=0Ahttps://authority/foo/user?tx=3D1zhd7896=
32uilos as elegant.=0A=0A-rick=0A=0A=0AOn Fri, Dec 16, 2011 at 9:10 AM, And=
y Parkins <andyparkins@gmail.com> wrote:=0A> On 2011 December 16 Friday, Ri=
ck Wesson wrote:=0A>> On Thu, Dec 15, 2011 at 4:07 PM, slush <slush@centrum=
.cz> wrote:=0A>> > I really like this proposal with standard URLs. All othe=
r proposals like=0A>> > DNS mapping or email aliases converted to URLs with=
some weird logic=0A>> > looks strange to me.=0A>>=0A>> wow, really. Maybe =
you could review some RFCs, there are thousands of=0A>> examples where some=
really smart engineers chose the exact opposite=0A>> path which you propos=
e below.=0A>=0A> Could you point me at an example?=0A>=0A>=0A> Andy=0A>=0A>=
--=0A> Dr Andy Parkins=0A> andyparkins@gmail.com=0A=0A--------------------=
----------------------------------------------------------=0ALearn Windows =
Azure Live!=A0 Tuesday, Dec 13, 2011=0AMicrosoft is holding a special Learn=
Windows Azure training event for =0Adevelopers. It will provide a great wa=
y to learn Windows Azure and what it =0Aprovides. You can attend the event =
by watching it streamed LIVE online.=A0 =0ALearn more at http://p.sf.net/sf=
u/ms-windowsazure=0A_______________________________________________=0ABitco=
in-development mailing list=0ABitcoin-development@lists.sourceforge.net=0Ah=
ttps://lists.sourceforge.net/lists/listinfo/bitcoin-development
--285087016-1047432035-1324060177=:10146
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:12pt"><div><span>You have t=
o be seriously joking to call the bitcoin protocol elegant. A message based=
system over TCP with constantly changing endians that needs to lookup its =
own IP address on several websites is not elegant. It is functioning, not e=
legant.</span></div><div><br><span></span></div><div><span>Also it is kind =
of dick to come guns blaring and start insulting slush who runs one of the =
biggest mining pools and is working on electrum, and sipa who develops the =
satoshi bitcoin.</span></div><div><br></div><div>Khalahan said:<br><span></=
span></div><div><span>> </span>Namecoin is a peer-to-peer generic name/v=
alue datastore system</div><div><br></div><div>Namecoin has the same proble=
m as DNS. From the document:</div><div><br></div><div>"The disadvantage of =
DNS TXT records is that updating a record takes =0Atime. This encourages pe=
ople to not use new addresses per transaction =0Awhich has certain security=
issues."</div><div><br></div> <div style=3D"font-family: times new roman,=
new york, times, serif; font-size: 12pt;"> <div style=3D"font-family: time=
s new roman, new york, times, serif; font-size: 12pt;"> <font face=3D"Arial=
" size=3D"2"> <hr size=3D"1"> <b><span style=3D"font-weight:bold;">From:</=
span></b> Rick Wesson <rick@support-intelligence.com><br> <b><span st=
yle=3D"font-weight: bold;">To:</span></b> Andy Parkins <andyparkins@gmai=
l.com> <br><b><span style=3D"font-weight: bold;">Cc:</span></b> bitcoin-=
development@lists.sourceforge.net <br> <b><span style=3D"font-weight: bold;=
">Sent:</span></b> Friday, December 16, 2011 5:41 PM<br> <b><span style=3D"=
font-weight: bold;">Subject:</span></b> Re: [Bitcoin-development] Fwd: [BIP=
15] Aliases<br> </font> <br>=0AIts a negative example -- in that the IETF =
does not specify anything<br>in the PATH part of the URI. The scheme, sure,=
but not in the path,<br>there are many types of URI schemes ( start with R=
FC 2396 )<br><br>There is significant upside to having your own scheme and =
having apps<br>understand how to integrate with it. Frankly, having just on=
e client<br>(I understand there are more) is an artifact that hinders accep=
tance<br>and participation. If you want to go the route of https then<br>sp=
ecifying a scheme is your path forward<br><br>I still believe that it is ex=
perience that is leading this thread down<br>the rat-hole of CGI and HTTP r=
equests. The stuff isn't magic, it is<br>just what you are used to. Review =
the bitcoin protocol, there is an<br>elegance there -- not found in t=
he https schemes proposed thus far.<br>CGI isn't a protocol, nor does it ad=
dress usability/identity issues.<br><br>Providing a mapping from <a
ymailto=3D"mailto:user@authority.tld" href=3D"mailto:user@authority.tld">u=
ser@authority.tld</a> addresses usability and<br>identity. I'd like to see =
an elegant transformation, specifically I<br>take to task anyone that advoc=
ates<br><a href=3D"https://authority/foo/user?tx=3D1zhd789632uilos" target=
=3D"_blank">https://authority/foo/user?tx=3D1zhd789632uilos</a> as elegant.=
<br><br>-rick<br><br><br>On Fri, Dec 16, 2011 at 9:10 AM, Andy Parkins <=
<a ymailto=3D"mailto:andyparkins@gmail.com" href=3D"mailto:andyparkins@gmai=
l.com">andyparkins@gmail.com</a>> wrote:<br>> On 2011 December 16 Fri=
day, Rick Wesson wrote:<br>>> On Thu, Dec 15, 2011 at 4:07 PM, slush =
<<a ymailto=3D"mailto:slush@centrum.cz" href=3D"mailto:slush@centrum.cz"=
>slush@centrum.cz</a>> wrote:<br>>> > I really like this propos=
al with standard URLs. All other proposals like<br>>> > DNS mappin=
g or email aliases converted to URLs with some weird logic<br>>> >=
looks strange
to me.<br>>><br>>> wow, really. Maybe you could review some RF=
Cs, there are thousands of<br>>> examples where some really smart eng=
ineers chose the exact opposite<br>>> path which you propose below.<b=
r>><br>> Could you point me at an example?<br>><br>><br>> An=
dy<br>><br>> --<br>> Dr Andy Parkins<br>> <a ymailto=3D"mailto:=
andyparkins@gmail.com" href=3D"mailto:andyparkins@gmail.com">andyparkins@gm=
ail.com</a><br><br>--------------------------------------------------------=
----------------------<br>Learn Windows Azure Live! Tuesday, Dec 13, =
2011<br>Microsoft is holding a special Learn Windows Azure training event f=
or <br>developers. It will provide a great way to learn Windows Azure and w=
hat it <br>provides. You can attend the event by watching it streamed LIVE =
online. <br>Learn more at http://p.sf.net/sfu/ms-windowsazure<br>____=
___________________________________________<br>Bitcoin-development
mailing list<br><a ymailto=3D"mailto:Bitcoin-development@lists.sourceforge=
.net" href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-dev=
elopment@lists.sourceforge.net</a><br><a href=3D"https://lists.sourceforge.=
net/lists/listinfo/bitcoin-development" target=3D"_blank">https://lists.sou=
rceforge.net/lists/listinfo/bitcoin-development</a><br><br><br> </div> </di=
v> </div></body></html>
--285087016-1047432035-1324060177=:10146--
|
