From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id E407F3B25E for ; Mon, 13 Jun 2016 10:58:17 -0400 (EDT) Received: by mail-oi0-x22f.google.com with SMTP id u201so84265531oie.0 for ; Mon, 13 Jun 2016 07:58:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=xrSekifNZF5e/nl+6p2BfkdzCWP4dKLuH+hZjxVfIGo=; b=Q/wi8NZ0VdFm81iPil5WMSd/5kvQWUyHlLI43/DFC2YhK/DYLai6apATDTGGIiPozD ipstEJ85Ky8AWzMQ1woeeirwrAlg2G2Ek/1UbpGUvJSbIsGsv5aXHDFzEvjPDRtMbz+u z644VRZNTshOwnr6q7PynKrtx4BEq7FqWHYjLt6xje1SB/TC4k9n7gNZqAE2JWAK/Pd/ gyZ69JIN1ai95IlVhXZBr0jDoPaBuAYJtIPCbR+AMAWlG3l2Jx+Sdug8elBVW/od1YM7 drMTn5pl4QDzyC/iT1Y5tlKZKWyBJofTr8Pp6YO2PLnViGwpOMeS8vavG+ytFeexW1HF xv6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=xrSekifNZF5e/nl+6p2BfkdzCWP4dKLuH+hZjxVfIGo=; b=Z7edbRzURAH+fnPYiN3wmtvwmcZmZqeM6VH+l61pEubD7Z1pB5hvTQzRM+MmqkH5ZQ TANpnKnfRtOibJfc99Fo+M/FDrX6V2Nnx3BosCX+/a4BlSIJ54rhm81iceTS7oiUq9su ByV4xpP4H/reHbOL4KY3IzwZOVGoGqlw66petiBBPck/hQFU9SOUPXsIsC/zJoBBr5Pn tdxNLWQWZI36XoqtBMkSeiKe7GVa8t+uTtehmudzw0/KSadK5IszXRkMtExqPsW90Suh RIJoAwKqLfnrEFln3QlKu2gvUd+q1JqqqBSyA1wYt2cPy93/F/N78zQVtKDvwh9NaDTt TCqA== X-Gm-Message-State: ALyK8tIH6Ax3b2z1B5hIbscZAal1njJKWA76IczNV36IJSKjQuyJ1exQI3PLRSILULdUrLQ+z+g79IPzFeHeqQ== X-Received: by 10.157.9.226 with SMTP id 31mr8215769otz.165.1465829897042; Mon, 13 Jun 2016 07:58:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.229.210 with HTTP; Mon, 13 Jun 2016 07:58:16 -0700 (PDT) In-Reply-To: <2BB7767C-F58D-4A91-9EDF-03C9DD31D882@gmail.com> 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> From: Dave Taht Date: Mon, 13 Jun 2016 07:58:16 -0700 Message-ID: To: Rich Brown Cc: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , bloat Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 14:58:18 -0000 On Sun, Jun 12, 2016 at 10:49 AM, Rich Brown wrot= e: > To all the Bufferbloaters out there... > > Thanks again to Toke for all this good work. It's terrific to see the pag= es 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've been thinking of the next steps - to make all this work really usefu= l. I see there are three important issues: > > Organizing: Thinking about the best way to display the current informatio= n: > - Should Cake be listed as a top-level project? "smart queue management" could, with cake mentioned prominently. Put in an overview for all the places fq_codel has made it to (edgerouters, sophos, BSD, openwrt, dd-wrt, (?) - what we know of certain commercial products when they did it right (adaptive qos), or didn't quite (streamboost). "cake" is such a terrible name googlejuicewise. I do periodically google for "cake shaper" and giggle at the results... which reminds me that somehow, someday, a logo(s) for the project(s) would be nice. > - Is there a way to display newest entries? I'd like to see a sid= ebar element showing the 5 newest posts Jim and I had hoped to build a "blog planet" one day that federated all the #bufferbloat tags from various sources. Since this is a manual process currently (I still have a daily google query for it), perhaps automating that with javascript to (somehow) grab the last twitter and g+ mentions, and a few key blogs, or building it on the fly on a build? > - Can an RSS feed be generated automatically? Yes. > Curating: The current site makes it seem as if all pages are equally impo= rtant. I feel the urge to do the following: > - Categorizing the "List of Wiki Pages" for a project (e.g., http= ://bufferbloat.net/projects/cerowrt/ ) > so there's a sense of their importance Um, I figured this would be just autogenerated from everything published. There are ways to mark the metadata as to priority. > - Discard old/outdated/useless articles or those that need work, remark to be draft: yes > Workflow: > - Rules for making posts: Who can make them? How do they get publ= ished? There is a difference between a "blog post/news item" and a wiki page. One reason why I intend to keep blog.cerowrt.org separate, is there I am trying to build upon the methods I was using with the old "deBloat" repository, "having a public lab notebook, chock full of opinions, wild theories, and mis-interpretations" - that this time, is replicated with all the data that backs (or doesn't back) all that up. I am still quite remorseful that all my private notes and data from the first 2 years of the effort was lost when my lab machines got stolen, there was plenty of stuff I did not publish there that I wish I could refer to now were I still trying for a PHD. The deBloat repo and various presentations are the only thing that survived from that era. Never again! but that means that that blog repo is going to get very, very big, and I'd prefer these sites to be primarily text and graphics, and thus smaller. I note that in blog.cerowrt.org I am preserving page authorship (and do invite other posters!). Toke has this stuff copyright "the bufferbloat community", which is a meaningless abstraction legally. the site overall was basically creative commons. I don't think anybody here cares. > - Auto-publish - if it's not already happening, could we re-rende= r and publish after a commit? > - I see the 404 handler in place, but it doesn't seem to show a l= ink to archive.org My plan for 404's long term was to have a page explaining this was a volunteer project, encouraging them to fix their own bloat, and contribute either work or cash. I thought about using a canned copy of this: http://www.dslreports.com/speedtest/results/bufferbloat?up=3D1 with the popular "you are here/you could be here" annotation. I wish there was some way to sample the tcp stats on the page load itself to measure the bloat the user experienced.... > - Is there a way to do page redirection? It looks as if Toke has = done a great job of replicating > URLs in the new site, but if we see frequent broken links= , is there a way to redirect a page to its equivalent on the new site? > - Should we add a Google search box on 404 page? On every page? I have missed having search, especially on the bug tracker. It was one of those bugs I thought I'd fix in "in a few weeks", 5 years ago. As the plan is to move to github's bug tracker, that's solved. As for indexing the site, well, I keep hoping that various non-google search technologies (like Xapian) had progressed in usability. Is there a way to embed something that uses no javascript? > - Would it make sense to review error logs from time to time? Sure, although we could add the linkchecker to people's local builds. 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'd love to have your thoughts. Thanks. > > Rich --=20 Dave T=C3=A4ht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org