From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] nearly 5 years of battling bufferbloat... and 15 years to go?
Date: Tue, 16 Jun 2015 12:49:19 -0700 [thread overview]
Message-ID: <CAA93jw7qfpugUc+c30pN_J1jQYT7K9V6+gb2vMevvtvjyWnsfw@mail.gmail.com> (raw)
We set out to boil an ocean, and it does appear to be, at least,
steaming slightly.
http://www.dslreports.com/speedtest/results/isp
A top perspective from all the members of this effort as to:
A) a review of what we are succeeding at.
B) what we are failing at.
C) what we should be prioritize in the future
D) how it should be structured
would be nice. 5 years from now, where should we be? How do we get
there? What's the end state?
Closing up shop entirely is also an option. There really aren't a lot
of barriers to doing that, mostly moving good content into wikipedia,
and getting the mailing list onto a stable server.
--
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
reply other threads:[~2015-06-16 19:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw7qfpugUc+c30pN_J1jQYT7K9V6+gb2vMevvtvjyWnsfw@mail.gmail.com \
--to=dave.taht@gmail.com \
--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