From: Michael Richardson <mcr@sandelman.ca>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Review of Delta's in-flight wifi mentions latency!
Date: Mon, 06 Feb 2023 18:45:21 +0100 [thread overview]
Message-ID: <2328666.1675705521@dyas> (raw)
In-Reply-To: <942C0D4A-BDAB-443E-AEE7-2852445EE995@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
I tried a few times to use KLM's in-flight wifi which is supposed to be for
text messaging only. I figure it ought to work for IMAP/SMTP too.
It never quite worked for me, although the price was right.
But, I think that it's a good niche for what are going to be unavoidably
dog-legged high-latency aircraft connections for the various LEO solutions
come to aircraft.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2023-02-06 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 15:30 Rich Brown
2023-02-06 17:45 ` Michael Richardson [this message]
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=2328666.1675705521@dyas \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.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