From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C83173B25E for ; Mon, 13 Jun 2016 11:15:12 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Filter: OpenDKIM Filter v2.10.3 mail2.tohojo.dk 10BE440472 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1465830909; bh=klgr+A07ysL0g1e6OTEu9suCnoNoQGmBOMT+29Modp0=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=tZZlJoZAafhUp/ETvXTEgn5LWshAw18B51zXsttsH0U0Va8D/oED2CUiiOjegXt43 qXwRSknzogPYt9giDMhMpi9qb1t9ClGhSe2u+FbMkcl1TgX9dwCNvavzw4KcyMQRn/ wk9xMsoNwnSIQ5TjZ9/b9GLG9NZItndTl3kfXdSw= Received: by alrua-kau.kau.toke.dk (Postfix, from userid 1000) id 02ABEC4010D; Mon, 13 Jun 2016 17:15:06 +0200 (CEST) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Dave Taht Cc: Rich Brown , bloat References: <86DAC1A9-D218-40A4-AD48-D9C0B4B01103@gmail.com> <87twh0j5dg.fsf@toke.dk> <87inxfk28r.fsf@toke.dk> <87wplvij9r.fsf@toke.dk> <2BB7767C-F58D-4A91-9EDF-03C9DD31D882@gmail.com> Date: Mon, 13 Jun 2016 17:15:06 +0200 In-Reply-To: (Dave Taht's message of "Mon, 13 Jun 2016 07:58:16 -0700") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87lh299l39.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Bloat] Bufferbloat.net - Organizing, curating, and workflow X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 15:15:13 -0000 Dave Taht writes: > On Sun, Jun 12, 2016 at 10:49 AM, Rich Brown wrote: >> To all the Bufferbloaters out there... >> >> Thanks again to Toke for all this good work. It's terrific to see the pages >> resurrected, and to have the www.bufferbloat.net site living again. > > And it's fast - even half a planet away. I am still looking around at > various cdn technologies.... I played around with using cloudfare through amazon for my blog at some point; for static pages you can get it to pull from an S3 bucket. Syncing to that is fairly straight forward. I gave up on the effort at the time because I botched the SSL cert setup (cloudfare only accepts up to 2048 bits, and this was pre-letsencrypt, so getting a new one once issued was non-trivial), and because the propagation delay for changes was too high. We can certainly stick it in a CDN if you find something that works well, but for now at least I'd call that a premature optimisation. I did configure the web server to do most of the obvious speed optimisations (for instance, everything will be statically compressed on build, so the server basically just has to do sendfile() on the right file on request). https://developers.google.com/speed/pagespeed/insights/?url=https://www.bufferbloat.net/projects/ > Definately agree it would be good to track what people have been using > as inbound links, on plain access also. People kept linking to the > oddest parts of the site... I can have the server generate awstats reports for the site (http://www.awstats.org/) - these include the most common inbound referrers and most common 404 pages. Not sure if they should be public, though. Don't *think* they usually contain sensitive content (given that the whole site is public, anyway). But I could be wrong; thoughts? -Toke