From: Dave Taht <dave.taht@gmail.com>
To: Kenneth Porter <shiva@sewingwitch.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] fcc input
Date: Fri, 26 Mar 2021 12:09:14 -0700 [thread overview]
Message-ID: <CAA93jw4wi52RiUgJMGa+OUJAPBMB7MoQcQMBUu1fvxXPvjh1Sg@mail.gmail.com> (raw)
In-Reply-To: <A82CBB923160F8F7F5DC395E@172.27.17.193>
I have often thought hard about trying to explain things better via
animations, and on more than one occasion tried to find an animator
who could turn this old 8m talk from "people as packets" into "unruly
animals as packets".
https://www.youtube.com/watch?v=Rb-UnHDw02o&t=1657s
But that requires both money and time, and I've usually had neither.
Grant money would be nice for a whole string of educational videos,
but not being part of the MICA complex has made that difficult. If I
ever get caught up on bills, and some other pressing problems, perhaps
we could do a kickstarter campaign to get some things animated.
On Fri, Mar 26, 2021 at 12:05 PM Kenneth Porter <shiva@sewingwitch.com> wrote:
>
> --On Friday, March 26, 2021 10:58 AM -0700 Aaron Wood <woody77@gmail.com>
> wrote:
>
> > I'm still surprised at how hard it is to get people to understand that the
> > problem they're having (especially with real-time video like Zoom) isn't
> > bandwidth, but jitter and bloat...
>
> Speed is easy to understand. I see a similar issue with space travel fans,
> who have trouble grasping how acceleration, not velocity, is the important
> factor in that domain. And when velocity is a factor, it's the vector, not
> the scalar, that counts. If only people got decent math educations....
>
> Jitter and bloat aren't intuitive and need a lot more thinking and patience
> to understand. Perhaps we need a good animated cartoon to explain it.
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
next prev parent reply other threads:[~2021-03-26 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 4:11 Dave Taht
2021-03-24 19:52 ` Jonathan Foulkes
2021-03-26 16:58 ` Aaron Wood
2021-03-26 19:04 ` Kenneth Porter
[not found] ` <A82CBB923160F8F7F5DC395E@172.27.17.193>
2021-03-26 19:09 ` Dave Taht [this message]
2021-03-26 19:22 ` Kenneth Porter
[not found] ` <5EDB17C519EAF0BFE3755CE4@172.27.17.193>
2021-03-26 19:37 ` Dave Taht
2021-03-27 8:54 ` Jan Ceuleers
2021-03-30 5:36 ` Matt Mathis
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=CAA93jw4wi52RiUgJMGa+OUJAPBMB7MoQcQMBUu1fvxXPvjh1Sg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=shiva@sewingwitch.com \
/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