General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Collier-Brown <davecb.42@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] "Mighty" browser cares about latency
Date: Thu, 29 Apr 2021 22:22:44 -0400	[thread overview]
Message-ID: <dc827eb8-0c81-23f3-67cd-0cb7f1a62a21@indexexchange.com> (raw)
In-Reply-To: <mailman.2690.1619694013.24343.bloat@lists.bufferbloat.net>

Of course, it's unclear what they've done toward "building a custom 
low-latency networking protocol", as the blog post at 
https://blog.mightyapp.com/mightys-secret-plan-to-invent-the-future-of-computing/ 
is all marketing-announcement razzle-dazzle.

--dave

David Collier-Brown,                                 | Always do right. 
This will gratify
System Programmer and Author              | some people and astonish the 
rest
dave.collier-brown@indexexchange.com | -- Mark Twain



           reply	other threads:[~2021-04-30  2:22 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.2690.1619694013.24343.bloat@lists.bufferbloat.net>]

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=dc827eb8-0c81-23f3-67cd-0cb7f1a62a21@indexexchange.com \
    --to=davecb.42@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.collier-brown@indexexchange.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