From: Rich Brown <richb.hanover@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Review of Delta's in-flight wifi mentions latency!
Date: Mon, 6 Feb 2023 10:30:55 -0500 [thread overview]
Message-ID: <942C0D4A-BDAB-443E-AEE7-2852445EE995@gmail.com> (raw)
In this ZDnet article, they showed a screenshot of speedtest.net while using Delta's in-flight wifi. It showed pretty big latency.
https://www.zdnet.com/home-and-office/networking/i-tried-deltas-new-free-inflight-wi-fi-heres-how-fast-it-was/
BUT... the good news is that the reviewer commented on it.
> With ping rates of 600 to 1,000 milliseconds, however, it's absolutely unusable for videoconferencing with Zoom and the like,
> and only a glutton for punishment would use it for gaming.
They said other services "worked as well as in the lobby of a trade-show hotel". (That's damning with faint praise...)
Nonetheless, this is PROGRESS! Someone in the main stream press acknowledged that latency might be a thing. And that it could harm your network access!
Rich
next reply other threads:[~2023-02-06 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 15:30 Rich Brown [this message]
2023-02-06 17:45 ` Michael Richardson
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=942C0D4A-BDAB-443E-AEE7-2852445EE995@gmail.com \
--to=richb.hanover@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