From: David Collier-Brown <davec-b@rogers.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Seen in passing: mention of Valve's networking scheme and RFC 5348
Date: Mon, 2 Apr 2018 08:46:56 -0400 [thread overview]
Message-ID: <50e57074-4ca5-59f7-f010-d9b2b845a8a7@rogers.com> (raw)
In-Reply-To: <tag:www.oreilly.com, 2018-04-02:/ideas/four-short-links-2-april-2018@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]
This is not an initiative I know about, but it mentions Reno and it's
inability to use SACK, so it sounds at first hearing to be another dumb
gamer thing. Opinions, anyone?
--dave (I used to work for World Gaming) c-b
-------- Forwarded Message --------
Subject: Four short links: 2 April 2018
Date: Mon, 02 Apr 2018 11:40:00 GMT
From: Nat Torkington <>
https://www.oreilly.com/ideas/four-short-links-2-april-2018
Four short links: 2 April 2018
/Game Networking, Grep JSON, Voting Ideas, and UIs from Pictures/
1. Valve's Networking Code
<https://github.com/ValveSoftware/GameNetworkingSockets> -- /a basic
transport layer for games. The features are: connection-oriented
protocol (like TCP)...but message-oriented instead of
stream-oriented; mix of reliable and unreliable messages; messages
can be larger than underlying MTU, the protocol performs
fragmentation and reassembly, and retransmission for reliable;
bandwidth estimation based on TCP-friendly rate control (RFC 5348);
encryption; AES per packet, Ed25519 crypto for key exchange and cert
signatures; the details for shared key derivation and per-packet IV
are based on Google QUIC; tools for simulating loss and detailed
stats measurement./
2. gron <https://github.com/tomnomnom/gron/> -- grep JSON from the
command line.
3. The Problem With Voting
<https://medium.com/@nayafia/the-problem-with-voting-8cff39f771e8>
-- I don't agree with all of the analysis, but the proposed
techniques are interesting. I did like the term "lazy consensus"
/where consensus is assumed to be the default state (i.e., “default
to yes”). The underlying theory is that most proposals are not
interesting enough to discuss. But if anyone does object, a
consensus seeking process begins./ (via Daniel Bachhuber
<https://danielbachhuber.com/2018/03/30/nothing-is-sacred/>)
4. pix2code <https://arxiv.org/abs/1705.07962> -- open source
<https://github.com/tonybeltramelli/pix2code> code that generates
Android, iOS, and web source code for a UI from just a photo. It's
not coming for your job any time soon (/over 77% of accuracy/), but
it's still a nifty idea. (via Two Minute Papers <http://bit.ly/2uGxWu3>)
Continue reading Four short links: 2 April 2018.
<https://www.oreilly.com/ideas/four-short-links-2-april-2018>
[-- Attachment #2: Type: text/html, Size: 4208 bytes --]
next parent reply other threads:[~2018-04-02 12:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tag:www.oreilly.com, 2018-04-02:/ideas/four-short-links-2-april-2018@localhost.localdomain>
2018-04-02 12:46 ` David Collier-Brown [this message]
2018-04-03 11:54 ` Jesper Louis Andersen
2018-04-03 12:14 ` Jonathan Morton
2018-04-03 12:35 ` Mikael Abrahamsson
2018-04-03 14:27 ` Michael Welzl
2018-04-03 14:48 ` Jesper Louis Andersen
2018-04-03 15:04 ` Jim Gettys
2018-04-04 12:45 ` Jesper Louis Andersen
2018-04-04 13:39 ` David Collier-Brown
2018-04-03 16:14 ` Michael Welzl
2018-04-04 7:01 ` Mikael Abrahamsson
2018-04-04 7:42 ` Dave Taht
2018-04-04 7:55 ` Michael Welzl
2018-04-04 8:53 ` Mikael Abrahamsson
2018-04-04 8:52 ` Mikael Abrahamsson
2018-04-04 9:56 ` Luca Muscariello
2018-04-04 10:52 ` Mikael Abrahamsson
2018-04-04 11:06 ` Luca Muscariello
2018-04-05 0:04 ` Marcelo Ricardo Leitner
2018-04-04 19:23 ` Michael Richardson
2018-04-04 19:38 ` Michael Welzl
2018-04-05 0:08 ` Marcelo Ricardo Leitner
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=50e57074-4ca5-59f7-f010-d9b2b845a8a7@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.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