From: "Christian T. Steigies" <cts@debian.org>
To: John Alexander <acontractornow@yahoo.co.uk>
Cc: Carsten Strotmann <cas@strotmann.de>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Debian m68k <debian-68k@lists.debian.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: Planning a Debian/Linux m68k Meeting in 2020
Date: Fri, 10 Apr 2020 16:54:32 +0200 [thread overview]
Message-ID: <20200410145431.GA22380@winslow.earth.sol> (raw)
In-Reply-To: <1802398089.6357995.1586526646576@mail.yahoo.com>
On Fri, Apr 10, 2020 at 01:50:46PM +0000, John Alexander wrote:
> Hi there I like the idea of Jitsi as it's much more open but from the use we have had with local LUGs we have found it to be problematic with a larger number of clients particularly
> low bandwidth clients essentially bringing the server into a bad state.
>
> The sessions run on Zoom work much better.. I can gain access to both platforms to both platforms and we can try them out together and let you make up your own minds.
Please no zoom. It's been all over the news...
We use BigBlueButton for teaching now, I had a successful meeting with more
than 180 participants (no camera, no mike for the participants). A session
with 12 parallel video streams also worked fined. The server has a 1Gbit/s
connection, I have a simple DSL connection.
In case somebody has time to waste, you can help packaging it for Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956252
Christian
next prev parent reply other threads:[~2020-04-10 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 8:04 Planning a Debian/Linux m68k Meeting in 2020 Carsten Strotmann
2020-04-10 12:05 ` John Paul Adrian Glaubitz
[not found] ` <1802398089.6357995.1586526646576@mail.yahoo.com>
2020-04-10 14:54 ` Christian T. Steigies [this message]
2020-05-20 20:36 ` Carsten Strotmann
2020-05-20 20:51 ` John Paul Adrian Glaubitz
2020-06-01 10:50 ` Carsten Strotmann
2020-06-02 7:16 ` John Paul Adrian Glaubitz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200410145431.GA22380@winslow.earth.sol \
--to=cts@debian.org \
--cc=acontractornow@yahoo.co.uk \
--cc=cas@strotmann.de \
--cc=debian-68k@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@lists.linux-m68k.org \
/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