From: Dave Taht <dave.taht@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Bandwidith rate by host instead of global while using [dual-]srchost and [dual-]dsthost
Date: Tue, 12 Jun 2018 11:55:00 -0700 [thread overview]
Message-ID: <CAA93jw7NkpC=vnrtHwLrrSw+uRXgg16McKpoFniDAbqQySPufA@mail.gmail.com> (raw)
In-Reply-To: <6500246E-2382-48FD-8FC7-A15452D42042@heistp.net>
On Mon, Jun 11, 2018 at 11:55 PM, Pete Heist <pete@heistp.net> wrote:
>
> On Jun 11, 2018, at 10:17 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
> I long ago ran out of motivation and money to continue working on
> bufferbloat. It's fixed enough,
> for those that care. It's on enough devices (more every day) now to
> give those that succeed some market advantage.
>
>
> Any thoughts on worthy work beyond bloat?
I gave into despair when the shuttleworth grant didn't come through
last year. I'm glad y'all keep slogging on.
I started at this as a third world problem. Living in the first world
is thus far proving too expensive.
Unless I get my act together on $dayjob soon even moving back to
Nicaragua will be impossible. (and Nica is currently very dicy
politically)
I'm still primarily motivated by fixing the internet outside the usa.
My daydream, once I had
enough cash in the bank or some (say, 50k) maintenence level of
income, was to sail
from pacific island to pacific island, updating uplinks along the way,
finishing up writing a few papers,
contemplating some other currently insoluable networking problems -
like routing.
These days... I don't know. I'm at a cusp. If I keep failing at dayjob
for another month I'll try to find something
outside this field entirely. Last year, being dead broke, I did
construction for a while. It was good for me.
> Heaving cake over the transom is the "last" thing. And after 18
> versions in the last round, toke's fried, I'm fried, everybody's
> fried. I'm very happy it started cracking 40gbits, stumped at the bug
> stopping us.
>
>
> I wish I could even reproduce that, then I’d at least take a caveman
> approach to solving it.
>
> I *am* going to washington DC week after next for the lanman2018
>
> presentation of cake, and perhaps I'll find a way to raise some hell
> with the FCC, congress, or the FTC (suggestions wanted), but...
>
>
> Please do.
The only idea I have at the moment is to stand outside the ftc's offices in
a zoot suit with guitar and empty violin case.
>
> I feel we need a re-decentralization of the Internet’s infrastructure and
> services, and the FCC’s actions are not helping. I’m not sure how to get
> that across when the only language spoken is money.
Obama's FTC seemed like a better place than the FCC for many issues.
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-06-12 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 15:43 Michel Blais
2018-06-11 17:44 ` Dave Taht
2018-06-11 19:44 ` Toke Høiland-Jørgensen
2018-06-11 19:54 ` Stephen Hemminger
2018-06-11 20:17 ` Dave Taht
2018-06-12 6:55 ` Pete Heist
2018-06-12 18:55 ` Dave Taht [this message]
2018-06-16 15:33 ` Michel Blais
2018-06-16 19:20 ` Pete Heist
2018-06-16 19:26 ` Pete Heist
2018-06-17 13:35 ` Toke Høiland-Jørgensen
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7NkpC=vnrtHwLrrSw+uRXgg16McKpoFniDAbqQySPufA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=pete@heistp.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