summaryrefslogtreecommitdiff
path: root/82/df4d52497fad5a24ca2799ea202ed136f1b71d
blob: eccf80f592422702101f3f12960fd43ddc896387 (plain)
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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1WagjY-00040F-9O
	for bitcoin-development@lists.sourceforge.net;
	Thu, 17 Apr 2014 07:27:44 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.171 as permitted sender)
	client-ip=209.85.213.171; envelope-from=laanwj@gmail.com;
	helo=mail-ig0-f171.google.com; 
Received: from mail-ig0-f171.google.com ([209.85.213.171])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WagjX-0005xy-Go
	for bitcoin-development@lists.sourceforge.net;
	Thu, 17 Apr 2014 07:27:44 +0000
Received: by mail-ig0-f171.google.com with SMTP id c1so1981999igq.4
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 17 Apr 2014 00:27:38 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.50.146 with SMTP id c18mr9108688igo.42.1397719658195;
	Thu, 17 Apr 2014 00:27:38 -0700 (PDT)
Received: by 10.64.70.131 with HTTP; Thu, 17 Apr 2014 00:27:38 -0700 (PDT)
In-Reply-To: <CACKnu1prEkZb5L4bGeKfjHtW+1CLmAuYr2-OWq0z5z+SvxhLTg@mail.gmail.com>
References: <CA+s+GJDdENtqQt1f+L5htuuyPxUxsq0prLQFBLirTjJz0nG1gw@mail.gmail.com>
	<CACKnu1prEkZb5L4bGeKfjHtW+1CLmAuYr2-OWq0z5z+SvxhLTg@mail.gmail.com>
Date: Thu, 17 Apr 2014 09:27:38 +0200
Message-ID: <CA+s+GJCSCLz2sizKE_AqZssqCS_fVpJyNDL7PTvc4cBvtukrRA@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Ben Carroll <ben@q9y.net>
Content-Type: multipart/alternative; boundary=047d7bdca61eb8f1ca04f737f75b
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
	(laanwj[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: 1WagjX-0005xy-Go
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Warning message when running wallet in
 Windows XP (or drop support?)
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, 17 Apr 2014 07:27:44 -0000

--047d7bdca61eb8f1ca04f737f75b
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 16, 2014 at 10:14 PM, Ben Carroll <ben@q9y.net> wrote:

While forcefully dropping XP support would seem like a waste of time, and
> somewhat arbitrary.  If windows builds just stops working for XP, it just
> stops working, however I don't foresee that happening.  I would make a
> reasonable guess that the client probably would even run without fuss on
> Win2k.
>

The _WIN32_WINNT define that is used (0x0501) makes Windows XP the lowest
version that the software will run on. It would be trivial to bump this to
Windows Vista (0x0600).

But in that case the user won't get a helpful message, the software will
outright refuse to run. So I thought, maybe it makes sense to show a
message that XP support is going to be removed - which must happen sooner
or later.

The insecurity of the platform adds urgence to this. So I thought "let's
ask for advice on the mailing list".

But what I get is contortions into unrelated topics (what does auto-update
have to do with this?), paranoid banter about 'manipulating users',
diversions into other topics. Sure, there's a thin line between being
helpful and being seen as manipulative, but it's over the top to compare
this with in-browser banners. It could be so much as a one-time message.

But it's time to close this issue. I'll do nothing here. I will however
stop testing on a Windows XP VM myself.

Wladimir

--047d7bdca61eb8f1ca04f737f75b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Wed, Apr 16, 2014 at 10:14 PM, Ben Carroll <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ben@q9y.net" target=3D"_blank">ben@q9y.net</a>&gt;</span> wrote:=
<br><br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir=3D"ltr">While forcefully dropping XP support would seem like a was=
te of time, and somewhat arbitrary. =C2=A0If windows builds just stops work=
ing for XP, it just stops working, however I don&#39;t foresee that happeni=
ng. =C2=A0I would make a reasonable guess that the client probably would ev=
en run without fuss on Win2k.</div>
</blockquote><div><br></div><div>The _WIN32_WINNT define that is used (0x05=
01) makes Windows XP the lowest version that the software will run on. It w=
ould be trivial to bump this to Windows Vista (0x0600).<br><br></div><div>
But in that case the user won&#39;t get a helpful message, the software wil=
l outright refuse to run. So I thought, maybe it makes sense to show a mess=
age that XP support is going to be removed - which must happen sooner or la=
ter.<br>
<br></div><div>The insecurity of the platform adds urgence to this. So I th=
ought &quot;let&#39;s ask for advice on the mailing list&quot;.<br><br></di=
v><div>But what I get is contortions into unrelated topics (what does auto-=
update have to do with this?), paranoid banter about &#39;manipulating user=
s&#39;, diversions into other topics. Sure, there&#39;s a thin line between=
 being helpful and being seen as manipulative, but it&#39;s over the top to=
 compare this with in-browser banners. It could be so much as a one-time me=
ssage.<br>
<br>But it&#39;s time to close this issue. I&#39;ll do nothing here. I will=
 however stop testing on a Windows XP VM myself.<br><br></div><div>Wladimir=
<br></div></div><br></div></div>

--047d7bdca61eb8f1ca04f737f75b--