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
205
206
207
208
209
210
211
212
213
214
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <thiagocmartinsc@gmail.com>) id 1R6sBB-000206-Gp
for bitcoin-development@lists.sourceforge.net;
Thu, 22 Sep 2011 22:55:41 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.175 as permitted sender)
client-ip=209.85.220.175;
envelope-from=thiagocmartinsc@gmail.com;
helo=mail-vx0-f175.google.com;
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R6sBA-0001I0-Pz
for bitcoin-development@lists.sourceforge.net;
Thu, 22 Sep 2011 22:55:41 +0000
Received: by vcbfl17 with SMTP id fl17so1321234vcb.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 22 Sep 2011 15:55:35 -0700 (PDT)
Received: by 10.220.108.203 with SMTP id g11mr696194vcp.279.1316732135250;
Thu, 22 Sep 2011 15:55:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.202.3 with HTTP; Thu, 22 Sep 2011 15:55:05 -0700 (PDT)
In-Reply-To: <CAJNQ0su4LjanK_miyL3_BqUxxvgr90A_aUcw8E4UPVUtAykG-g@mail.gmail.com>
References: <CABsx9T2Y3CmBr=twHvFOEoQCVcSySZ+JyEQXcOseRKxJi3KoLw@mail.gmail.com>
<CAJSM8J0=Nykpsa0MLR8=-x3GOphuppY9RBqzx7omKWr8h0Sbuw@mail.gmail.com>
<CAJNQ0su4LjanK_miyL3_BqUxxvgr90A_aUcw8E4UPVUtAykG-g@mail.gmail.com>
From: =?ISO-2022-JP?B?TWFydGlueCAtIBskQiU4JSchPCVgJTobKEI=?=
<thiagocmartinsc@gmail.com>
Date: Thu, 22 Sep 2011 19:55:05 -0300
Message-ID: <CAJSM8J1=FWAJVqgQ0HG=0TQU25hrsym=edthsB+sMqfzqgR2GQ@mail.gmail.com>
To: John Smith <witchspace81@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043c09662f9c5504ad8f977d
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(thiagocmartinsc[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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
X-Headers-End: 1R6sBA-0001I0-Pz
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.4 Release Candidate 2
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
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: Thu, 22 Sep 2011 22:55:41 -0000
--f46d043c09662f9c5504ad8f977d
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Hi John!
Thank you for your answer...
I have "two kinds" of address, the "static address", which I created myself
for any personal reason, and the "dinamic address", which is the automatic
generated address when I receive some Bitcoin amount, I label each one (the
automatic created by the software) with something like "DINAMIC-1",
"DINAMIC-2" and so on...
I use my "dinamic address" in a "random" way, following the moon phase...
lol
My point is: I like to keep track of all my Bitcoin Address, they are all
my...
Please, leave this feature alive, as a option, disabled by default.
I don't know why people fear about their own address... It is all under
"Receiving" tab! There is nothing to fear about it.
---
BTW, I think this option should have some explanations at the "Options
screen", for example:
For increasing your anonymity, enable the "Dinamic Bitcoin Address" option
and make sure to always use one new and different address for each
transaction. And do not link each address with your person!
(X) Dynamic Bitcoin Address (a new Bitcoin Address will be created
automatically for you, after each new received Bitcoin amount)
---
Thank you so much!
Best,
Thiago
2011/9/22 John Smith <witchspace81@gmail.com>
>
>
> 2011/9/22 Martinx - $B%8%'!<%`%:(B <thiagocmartinsc@gmail.com>
>
>> Hi everybody!!
>>
>> This is my first message here... I'm ThiagoCMC at bitcointalk...
>>
>> Well, one of the features that I like most is that, every time I receive
>> some Bitcoin amount, a new address appear at my "AddressBook"automatically,
>> AND, I like to track it.
>>
>
> Can I ask your rationale for this?
>
> From what I've noticed, most people's workflow is to create a new receiving
> address for each new contact that sends them bitcoins (either for every
> transaction, or they reuse the address for this person). To make sure that
> the address is labeled, they create it themselves and then give out the
> generated address.
>
> They are utterly spooked by suddenly appearing unlabeled addresses, of
> which they are unsure whether they are used, and which can never be removed.
>
> I'm fine with adding it back as an option but please leave it disabled by
> default...
>
> JS
>
>
--f46d043c09662f9c5504ad8f977d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div><div>Hi John!</div><div><br></div><div>=C2=A0Thank you for your answer=
...</div><div><br></div><div>=C2=A0I have "two kinds" of address,=
the "static address", which I created myself for any personal re=
ason, and the "dinamic address", which is the automatic generated=
address when I receive some Bitcoin amount, I label each one (the automati=
c created by the software) with something like "DINAMIC-1", "=
;DINAMIC-2" and so on...</div>
<div><br></div><div>=C2=A0I use my "dinamic address" in a "r=
andom" way, following the moon phase... lol</div><div><br></div><div>=
=C2=A0My point is: I like to keep track of all my Bitcoin Address, they are=
all my...</div>
<div><br></div><div>=C2=A0Please, leave this feature alive, as a option, di=
sabled by default.</div><div><br></div><div>=C2=A0I don't know why peop=
le fear about their own address... It is all under "Receiving" ta=
b! There is nothing to fear about it.</div>
<div><br></div><div>=C2=A0---</div><div><br></div><div>=C2=A0BTW,=C2=A0I th=
ink this option should have some explanations at the "Options screen&q=
uot;, for example:</div><div><br></div><div><div>=C2=A0For increasing your =
anonymity, enable the "Dinamic Bitcoin Address" option and make s=
ure to always use one new and different address for each transaction. And d=
o not link each address with your person!</div>
</div><div><br></div><div>=C2=A0(X) Dynamic Bitcoin Address (a new Bitcoin =
Address will be created automatically for you, after each new received Bitc=
oin amount)</div><div><br></div><div>=C2=A0---</div><div><br></div><div>=C2=
=A0Thank you so much!</div>
<div><br></div><div>Best,</div><div>Thiago</div><div><br></div><div class=
=3D"gmail_quote">2011/9/22 John Smith <span dir=3D"ltr"><<a href=3D"mail=
to:witchspace81@gmail.com">witchspace81@gmail.com</a>></span><br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">
<br><br><div class=3D"gmail_quote"><div class=3D"im">2011/9/22 Martinx - =
=E3=82=B8=E3=82=A7=E3=83=BC=E3=83=A0=E3=82=BA <span dir=3D"ltr"><<a href=
=3D"mailto:thiagocmartinsc@gmail.com" target=3D"_blank">thiagocmartinsc@gma=
il.com</a>></span><br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Hi everybody!!</div><div><br></div><div>=C2=A0This is my first message=
here... I'm ThiagoCMC at bitcointalk...</div><div><br></div><div>=C2=
=A0Well, one of the features that I like most is that, every time I receive=
some Bitcoin amount, a new address appear at my "AddressBook"aut=
omatically, AND, I like to track it.</div>
</blockquote></div><div><br>Can I ask your rationale for this?<br><br>From =
what I've noticed, most people's workflow is to create a new receiv=
ing address for each new contact that sends them bitcoins (either for every=
transaction, or they reuse the address for this person).=C2=A0 To make sur=
e that the address is labeled, they create it themselves and then give out =
the generated address.<br>
<br>They are utterly spooked by suddenly appearing unlabeled addresses, of =
which they are unsure whether they are used, and which can never be removed=
.<br><br>I'm fine with adding it back as an option but please leave it =
disabled by default...<br>
<font color=3D"#888888">
<br>JS<br><br></font></div></div>
</blockquote></div><br></div>
--f46d043c09662f9c5504ad8f977d--
|
