Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1Z2cQa-0001RB-3v
	for bitcoin-development@lists.sourceforge.net;
	Wed, 10 Jun 2015 09:36:08 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.44 as permitted sender)
	client-ip=74.125.82.44; envelope-from=laanwj@gmail.com;
	helo=mail-wg0-f44.google.com; 
Received: from mail-wg0-f44.google.com ([74.125.82.44])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Z2cQZ-00064A-2e
	for bitcoin-development@lists.sourceforge.net;
	Wed, 10 Jun 2015 09:36:08 +0000
Received: by wgbgq6 with SMTP id gq6so31195258wgb.3
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 10 Jun 2015 02:36:01 -0700 (PDT)
X-Received: by 10.194.61.212 with SMTP id s20mr4521504wjr.18.1433928961060;
	Wed, 10 Jun 2015 02:36:01 -0700 (PDT)
Received: from amethyst.visucore.com (dhcp-089-098-016-041.chello.nl.
	[89.98.16.41])
	by mx.google.com with ESMTPSA id r9sm13580902wjo.26.2015.06.10.02.35.59
	(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
	Wed, 10 Jun 2015 02:35:59 -0700 (PDT)
Date: Wed, 10 Jun 2015 11:35:57 +0200
From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: xor <xor@freenetproject.org>
Message-ID: <20150610093556.GA11409@amethyst.visucore.com>
References: <1943127.DBnVxmfOIh@1337h4x0r>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1943127.DBnVxmfOIh@1337h4x0r>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Spam-Score: -1.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
	-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: 1Z2cQZ-00064A-2e
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough
 to host this list?
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: Wed, 10 Jun 2015 09:36:08 -0000

On Wed, Jun 10, 2015 at 10:25:12AM +0200, xor wrote:
> http://www.howtogeek.com/218764/warning-don%E2%80%99t-download-software-from-sourceforge-if-you-can-help-it/

All our downloads (even old ones) have recently been deleted from sourceforge, for this reason. They haven't been mentioned in Bitcon Core release announcements for a long time.

No opinion on the mailing list. Though I think it's less urgent. The issue of moving the mailinglist has come up before a few times and people can't agree where to move to.

Wladimir