Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	"Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: [NNagain] my understanding latency talk
Date: Mon, 11 Dec 2023 13:55:43 -0800	[thread overview]
Message-ID: <CAA93jw5tW6JjRVTus0-cuqhiYjpgOje5M6Pao0DVS2W=9WA-fA@mail.gmail.com> (raw)

I am very pleased with all the talks given so far in the understanding
latency conference (I hope many of you are attending?), so much so
that I no longer know what to say wednesday morning. I wanted to wax
philosophical, and look forward to a brighter future next year... and
I enjoyed collaborating with y'all on the fcc filing (more sigs
wanted!)

Anyway if anyone would like to pull out a favorite before/after graph,
or share a story, or help find a way to focus this on no more than
three points, all the help is tremendously appreciated for the past 14
years. Me, I have been reflecting on Zen and the art of motorcycle
maintenance and on the ideas of "flow",

"Flow is a state of mind that occurs when a person is totally immersed
in an activity. It can occur during a wide variety of tasks such as
when a person is learning, being creative, or participating in a
sport. When in a flow state, people pay no attention to distractions
and time seems to pass without any notice." - which at the moment I do
not actually have, having had way too many distractions over the past
few weeks. I keep hoping for some universal enlightenment experience,
a lightbulb moment for networked humanity.

https://docs.google.com/presentation/d/1Rk2b7RXh5-KqQyOAkRbg9dgC3ZmZodR3rZlL5lNQv34/edit?usp=sharing

-- 
:( My old R&D campus is up for sale: https://tinyurl.com/yurtlab
Dave Täht CSO, LibreQos

                 reply	other threads:[~2023-12-11 21:55 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/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw5tW6JjRVTus0-cuqhiYjpgOje5M6Pao0DVS2W=9WA-fA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=nnagain@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