From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bufferbloat.net is sorely missed.
Date: Fri, 10 Jun 2016 18:08:09 +0100 [thread overview]
Message-ID: <575AF3F9.1070908@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <BCFB69E1-164E-48A5-845A-CF010E86BC17@gmail.com>
On 10/06/16 17:19, Rich Brown wrote:
> Hi Dave,
>
> I'm worried that the bufferbloat project appears MIA right now.
Absolutely. And the sqm-scripts also mention going to bufferbloat.net,
so hitting a 404 is underwhelming, especially as LEDE users have no
'CAKE' man pages to which to refer.
>
> It won't take much time to get that github page (http://richb-hanover.github.io/bufferbloat-site) running as www.bufferbloat.net. To do this:
>
> - You would have to set up A records for bufferbloat.net to point to 192.30.252.153 and 192.30.252.154
> - Wildcard address (for www.bufferbloat.net) should CNAME to the 'bufferbloat.net' A record
> - I would add a file (named 'CNAME') to the gh-pages branch of the github repo at https://github.com/richb-hanover/bufferbloat-site
>
> One DNS TTL later, we should have a bufferbloat.net web presence back on the air.
>
> Longer term, I don't have a preference about the web publishing system: I just want us to appear alive. Thanks.
Agree 100%
>
> Rich
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2016-06-10 17:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1225.1465559858.3642.bloat@lists.bufferbloat.net>
2016-06-10 15:27 ` Rich Brown
2016-06-10 15:47 ` Dave Taht
2016-06-10 16:19 ` Rich Brown
2016-06-10 17:08 ` Kevin Darbyshire-Bryant [this message]
2016-06-10 17:13 ` Outback Dingo
2016-06-10 18:05 ` Dave Taht
2016-06-10 18:17 ` Steinar H. Gunderson
2016-06-10 18:18 ` Rich Brown
2016-06-10 18:23 ` Dave Taht
2016-06-11 12:07 ` Toke Høiland-Jørgensen
2016-06-11 17:58 ` Dave Taht
2016-06-11 18:29 ` Toke Høiland-Jørgensen
2016-06-11 18:32 ` Toke Høiland-Jørgensen
2016-06-11 19:09 ` Dave Taht
2016-06-11 19:24 ` [Bloat] bufferbloat.net is sorely missed/Now it's back! Rich Brown
2016-06-11 20:05 ` Toke Høiland-Jørgensen
2016-06-11 21:31 ` Dave Taht
2016-06-12 17:49 ` [Bloat] Bufferbloat.net - Organizing, curating, and workflow Rich Brown
2016-06-12 18:02 ` Toke Høiland-Jørgensen
2016-06-12 18:13 ` moeller0
2016-06-12 18:16 ` Toke Høiland-Jørgensen
2016-06-12 18:24 ` moeller0
2016-06-12 18:25 ` Toke Høiland-Jørgensen
2016-06-12 18:27 ` Dave Taht
2016-06-12 18:33 ` Toke Høiland-Jørgensen
2016-06-13 13:25 ` Rich Brown
2016-06-13 14:05 ` Toke Høiland-Jørgensen
2016-06-13 15:13 ` [Bloat] Bufferbloat.net & LinkChecker Rich Brown
2016-06-13 19:18 ` Toke Høiland-Jørgensen
2016-06-13 14:58 ` [Bloat] Bufferbloat.net - Organizing, curating, and workflow Dave Taht
2016-06-13 15:15 ` Toke Høiland-Jørgensen
2016-06-13 15:39 ` Dave Taht
2016-06-13 10:33 ` [Bloat] bufferbloat.net is sorely missed/Now it's back! Kevin Darbyshire-Bryant
2016-06-13 11:10 ` Toke Høiland-Jørgensen
2016-06-10 8:44 [Bloat] bufferbloat.net is sorely missed Kevin Darbyshire-Bryant
2016-06-10 9:02 ` Toke Høiland-Jørgensen
2016-06-10 11:57 ` Kevin Darbyshire-Bryant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=575AF3F9.1070908@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox