From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VpoGu-0002dt-CC for bitcoin-development@lists.sourceforge.net; Mon, 09 Dec 2013 00:00:24 +0000 X-ACL-Warn: Received: from mail-pb0-f44.google.com ([209.85.160.44]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VpoGr-00053O-NG for bitcoin-development@lists.sourceforge.net; Mon, 09 Dec 2013 00:00:24 +0000 Received: by mail-pb0-f44.google.com with SMTP id rq2so4252526pbb.17 for ; Sun, 08 Dec 2013 16:00:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=3ffpyiHO4KDpDZuZgKPuRJ9o6YbRFqvIe/93O2DR3tM=; b=h4GsoImbkvDw6SIRKCxTN739y43rOZfd/Z9R+hJU/Fpuihu3NBhHz929oAvN0g4mbP qPqVtSfRiD7uoOrQ3+UkDDOcANhZtHq8JF4UNvH4SmHhjXteoD1A48IxLlp1B/mFwYjr ITyCk7jtPB20uPCmSuz0cgShi9FKvNtCze5wDx82TrGFuBXd2oD/bi4G1qmli7e0iP7O 5DsOvZXe9Zq1g1PypV2zVRJh8iyqSnQQ3bbEh3ooZScwv0pWB5QG0TvFL+spY1RUTcWt u1Q9GOMOZ+0WcCszTfuRP+zlHlUUuX1zXvQzdJumce8CVq36wYUshQJJYmBsGvI17rWo l1DQ== X-Gm-Message-State: ALoCoQnrbOIe+aO6chajgZGKSU1YXSYcH2Ki9PrCWuR408DiC5aQqRHKAN9cAMqmGKyE3V68mlDP X-Received: by 10.66.7.68 with SMTP id h4mr17605390paa.0.1386545347518; Sun, 08 Dec 2013 15:29:07 -0800 (PST) Received: from [192.168.189.137] ([70.114.202.107]) by mx.google.com with ESMTPSA id og5sm13394691pbb.10.2013.12.08.15.29.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Dec 2013 15:29:06 -0800 (PST) Message-ID: <52A500C1.60503@intersango.com> Date: Sun, 08 Dec 2013 17:29:05 -0600 From: Patrick User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 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> <52A4E199.3000209@gmail.com> In-Reply-To: <52A4E199.3000209@gmail.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit 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 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: doubleclick.net] X-Headers-End: 1VpoGr-00053O-NG 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: Mon, 09 Dec 2013 00:00:24 -0000 Have you considered black lotus dedicated servers? On 12/08/2013 03:16 PM, Saïvann Carignan wrote: >> 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. > > ------------------------------------------------------------------------------ > Sponsored by Intel(R) XDK > Develop, test and display web and hybrid apps with a single code base. > Download it for free now! > http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development