Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <davet@teklibre.net>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink videoconference today at 1PM PDT
Date: Tue, 1 Jun 2021 12:26:08 -0700	[thread overview]
Message-ID: <7372ADF5-67E6-407D-8522-B2FE6EE115CD@teklibre.net> (raw)
In-Reply-To: <637E0107-95CA-46DE-8D52-DC7750EFAC37@teklibre.net>

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

I note for those attending today that donovan and I are behind a starlink terminal and despite our best efforts, it does tend to glitch occasionally. we would appreciate it if a few people here would drop in early so we can test some things.

> On Jun 1, 2021, at 8:59 AM, Dave Taht <davet@teklibre.net> wrote:
> 
> Sorry for the late notice, as this is a regularly scheduled bufferbloat “working latency” meeting. Today’s focus is on starlink. 
> 
> We have a very full agenda today, but all are invited here to attend to see the latest results from our work and to help us discuss next steps.
> 
> We’ve been using the following galene.org <http://galene.org/> based videoconferencing server for our meetings
> 
> https://tun.taht.net:8443/group/bufferbloat <https://tun.taht.net:8443/group/bufferbloat>
> 
> Use any login you like, with no password, chrome is best
> 
> TODAY’S AGENDA
> 
> 5 minutes Dave Taht Overview of where we are
> 
> 10 minutes introductions to various volunteers with dishy terminals
> 10 minutes discussing future plans this week
> 10 minutes ESR irtt updates
> 20 minutes open discussion
> 
> 


[-- Attachment #2: Type: text/html, Size: 2375 bytes --]

  reply	other threads:[~2021-06-01 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 15:59 Dave Taht
2021-06-01 19:26 ` Dave Taht [this message]
     [not found]   ` <64576217-0531-45F5-B8C6-74702A62A7F6@gmail.com>
2021-06-01 21:02     ` Dave Taht

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=7372ADF5-67E6-407D-8522-B2FE6EE115CD@teklibre.net \
    --to=davet@teklibre.net \
    --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