From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1T0G3z-0007RT-Sg for bitcoin-development@lists.sourceforge.net; Sat, 11 Aug 2012 18:05:27 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1T0G3x-0008P9-Kr for bitcoin-development@lists.sourceforge.net; Sat, 11 Aug 2012 18:05:27 +0000 Received: from ishibashi.localnet (unknown [97.96.85.141]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 8A480560517; Sat, 11 Aug 2012 18:05:23 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Sat, 11 Aug 2012 18:05:07 +0000 User-Agent: KMail/1.13.7 (Linux/3.4.4-gentoo-nestfix; KDE/4.8.3; x86_64; ; ) References: <50268BB0.8080001@bitminter.com> In-Reply-To: <50268BB0.8080001@bitminter.com> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208111805.09429.luke@dashjr.org> 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 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1T0G3x-0008P9-Kr Subject: Re: [Bitcoin-development] Version 0.7 release planning X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Aug 2012 18:05:27 -0000 On Saturday, August 11, 2012 4:43:28 PM Geir Harald Hansen wrote: > By the way, by far the most common support request I have at my pool is > users withdrawing coins and not seeing it in their wallet because it's > not up-to-date with the block chain. Might be worth adding something in > the bitcoin-qt GUI to make it more obvious that users can't see new > transactions and why. Bitcoin-Qt even delays showing generation until 2 confirms. > These two seem odd: > Use UPnP to map the listening port (default: 0) > Use UPnP to map the listening port (default: 1 when listening) The default depends on build options, so that should be correct.