From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Cc: Anthony Minessale II <anthm@freeswitch.org>,
Ken Rice <krice@freeswitch.org>
Subject: [Cake] mo bettah open source multi-party videoconferncing in an age of bloated uplinks?
Date: Fri, 27 Mar 2020 10:27:39 -0700 [thread overview]
Message-ID: <CAA93jw7u5xtq9fzx9iCMd5StW4A=rY7D74YYbKRgAo+5YVajHw@mail.gmail.com> (raw)
sort of an outgrowth of this convo:
https://lwn.net/SubscriberLink/815751/786d161d06a90f0e/
I imagine worldwide videoconferencing quality could be much better if
we could convince more folk to
finally install sqm or upgrade to a working docsis 3.1 solution, etc.
Maybe some rag somewhere will finally pick up on bufferbloat solutions
and run with it? Or we can write some articles? Or reach out to school
systems? Or?
I've been fiddling with jitsi, and am about to give freeswitch a try.
Last I looked freeswitch's otherwise pretty nifty conference bridge
didn't dynamically adjust at all due to e2e signalling, but that was
years ago. (?)
I have to admit that p2p multiparty videoconferencing seems more
plausible in a de-bufferbloated age, but
haven't explored what tools are available. (?)
There's also been this somewhat entertaining convo on the ietf mbone
list: https://mailarchive.ietf.org/arch/msg/mboned/2thFQk_IYn38XCZBQavhUmOd6tk/
Around me there has been this huge interest in "streaming". The user
agreement for these (see restream.io's) is scary - and the copyright
police have control... but I am very happy to report that even a
couple really lousy long distance fq_codel'd ath9k links work *really*
well (with facebook's implementation), where a non fq_codeled link
(ath10k) failed miserably... and setting up a reflector in nginx also
failed miserably.
Anyone working on the ath10k AQL backport for openwrt as yet?
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next reply other threads:[~2020-03-27 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 17:27 Dave Taht [this message]
2020-03-27 19:00 ` David P. Reed
2020-03-27 19:12 ` David Lang
2020-03-27 19:36 ` Dave Taht
2020-03-27 20:32 ` Dave Taht
2020-03-28 19:58 ` Toke Høiland-Jørgensen
2020-03-28 23:15 ` David P. Reed
2020-03-30 10:57 ` Toke Høiland-Jørgensen
2020-03-28 6:53 ` Anthony Minessale II
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7u5xtq9fzx9iCMd5StW4A=rY7D74YYbKRgAo+5YVajHw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=anthm@freeswitch.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=krice@freeswitch.org \
--cc=make-wifi-fast@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