From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] [Rpm] the grinch meets cloudflare's christmas present
Date: Thu, 5 Jan 2023 11:07:15 +0100 [thread overview]
Message-ID: <CAC=tZ0q9av9oNNL4cqe4V1Ba4euXzRQwc+b3N4B+UnccJgvpwA@mail.gmail.com> (raw)
When a user refers to "gigs" it can be also talking about the monthly
data cap volume in the cell phone or mobile subscription.
A user is mainly not aware of what can be done with the "gigs". You
understand what you get when you get minutes of phone calls or a
certain number of SMS, but "gigs" are consumed in a way the user
mostly does not understand. Sometimes it is translated to a volume of
WhatsApp messages, pictures, videos (in a certain resolution, DVD
quality, for example), so people understand a bit what they are paying
for.
Language is ambiguous. Data rate in bit/s is referred as communication
channel capacity by Shannon, not to speed, but speed in km/h is an
analogy for information "running" in bit/s that people maybe
understand better.
Then, there is the people that ask you how much a file "weights" to
refer to the amount of bytes it has, as if information has a kind of
inertial mass.
There is the technical language and then the non-technical people
language. Two worlds apart, sometimes.
Regards,
David
> Date: Wed, 4 Jan 2023 19:11:28 -0800
> From: "Dick Roy" <dickroy@alum.mit.edu>
> To: "'Dave Collier-Brown'" <dave.collier-Brown@indexexchange.com>
> Cc: <starlink@lists.bufferbloat.net>
> Subject: Re: [Starlink] [Rpm] the grinch meets cloudflare's christmas
> present
> Message-ID: <15EBCC5BF2474AAB82C050259229B5FB@SRA6>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
>
>
>
> _____
>
> From: Starlink [mailto:starlink-bounces@lists.bufferbloat.net] On Behalf Of
> Dave Collier-Brown via Starlink
> Sent: Wednesday, January 4, 2023 6:48 PM
> To: starlink@lists.bufferbloat.net
> Subject: Re: [Starlink] [Rpm] the grinch meets cloudflare's christmas
> present
>
>
>
> I think using "speed" for "the inverse of delay" is pretty normal English,
> if technically erroneous when speaking nerd or physicist.
>
> [RR] I’ve not heard of that usage before. The units aren’t commensurate
> either.
>
> Using it for volume? Arguably more like fraudulent...
>
> [RR] I don’t think that was Bob’s intent. I think “load volume” was meant
> to be a metaphor for “number of bits/bytes” being transported (“by the
> semi”).
>
> That said, aren’t users these days educated on “gigs” which they intuitively
> understand to be Gigabits per second (or Gbps)? Oddly enough, that is an
> expression of “data/information/communication rate” in the appropriate units
> with the nominal technically correct meaning.
>
> RR
>
> --dave
>
next reply other threads:[~2023-01-05 10:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 10:07 David Fernández [this message]
[not found] <mailman.2678.1672860038.1281.starlink@lists.bufferbloat.net>
2023-01-04 22:21 ` David P. Reed
2023-01-05 21:19 ` Christoph Paasch
2023-01-05 22:01 ` Dave Taht
2023-01-05 22:09 ` Sebastian Moeller
-- strict thread matches above, loose matches on Subject: below --
2023-01-04 17:26 [Starlink] " Dave Taht
2023-01-04 19:20 ` [Starlink] [Rpm] " jf
2023-01-04 20:02 ` rjmcmahon
2023-01-04 21:16 ` Ulrich Speidel
2023-01-04 23:54 ` Bruce Perens
2023-01-05 2:48 ` Dave Collier-Brown
2023-01-05 3:11 ` Dick Roy
2023-01-05 11:25 ` Sebastian Moeller
2023-01-06 0:01 ` Dick Roy
2023-01-06 9:43 ` Sebastian Moeller
2023-01-05 6:11 ` rjmcmahon
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=tZ0q9av9oNNL4cqe4V1Ba4euXzRQwc+b3N4B+UnccJgvpwA@mail.gmail.com' \
--to=davidfdzp@gmail.com \
--cc=starlink@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