From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VpmBf-00061Q-RK for bitcoin-development@lists.sourceforge.net; Sun, 08 Dec 2013 21:46:51 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.169 as permitted sender) client-ip=209.85.223.169; envelope-from=saivann@gmail.com; helo=mail-ie0-f169.google.com; Received: from mail-ie0-f169.google.com ([209.85.223.169]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VpmBe-0005G7-VN for bitcoin-development@lists.sourceforge.net; Sun, 08 Dec 2013 21:46:51 +0000 Received: by mail-ie0-f169.google.com with SMTP id e14so4927025iej.0 for ; Sun, 08 Dec 2013 13:46:45 -0800 (PST) X-Received: by 10.43.0.202 with SMTP id nn10mr186995icb.54.1386539205693; Sun, 08 Dec 2013 13:46:45 -0800 (PST) Received: from [192.168.1.100] ([199.192.237.161]) by mx.google.com with ESMTPSA id j16sm10823315igf.6.2013.12.08.13.46.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Dec 2013 13:46:44 -0800 (PST) Message-ID: <52A4E199.3000209@gmail.com> Date: Sun, 08 Dec 2013 16:16:09 -0500 From: =?windows-1252?Q?Sa=EFvann_Carignan?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <52A3C8A5.7010606@gmail.com> <1795f3067ba3fcdd0caf978cc59ff024.squirrel@fruiteater.riseup.net> <52A435EA.7090405@gmail.com> <201312081237.24473.luke@dashjr.org> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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 (saivann[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: bitcoin.org] -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: 1VpmBe-0005G7-VN Subject: Re: [Bitcoin-development] Dedicated server for bitcoin.org, your thoughts? 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: Sun, 08 Dec 2013 21:46:52 -0000 > Issues that would need to be resolved: > > 1) Who pays for it? Most obvious answer: Foundation. However there's > currently a fairly clear line between the foundation website and the > bitcoin.org website. I personally am fine with the > bitcoin foundation funding the website, it's a lot closer to the bitcoin > community than github. But some people might care. So next step would be > to contact the Foundation board and see if they're willing to fund it. Actually I might find way to fund it. But I needed to have ACK & comments from developers before anything. > 2) Anti-DoS? I assume github handles this at the moment, though I doubt > there's anything to be gained from DoSing the informational website That is a fair question, we will need anti-DDoS. Unless something better (and affordable) can be recommended, this would yet put another Bitcoin website under CloudFlare. > 4) Who admins it? Obviously, I thought it would be important that the server is owned by someone who can be trusted, with ssh access for all core developers. > 5) Who controls DNS for it? I'm not sure we'll get any change on this level. I have no idea if the domain is in good hands, except for the fact that nothing bad happened thus far. If anything, moving it to core developers (as intended when the domain was registered) would make more sense IMO. But again, is it possible, I don't know.