Documentation on video- or audo-conferencing software like Mumble,
Jitsi, or Big Blue Button.

> con·fer·ence | \ ˈkän-f(ə-)rən(t)s1a : a meeting ("an act or process
> of coming together") of two or more persons for discussing matters
> of common concern. [Merriam-Webster][]

[Merriam-Webster]: https://www.merriam-webster.com/dictionary/conference

While [howto/irc][] can also be used to hold a meeting or conference, it's
considered out of scope here.

[howto/irc]: howto/irc

[[_TOC_]]

# Tutorial

## Connecting to Big Blue Button with a web browser

The Tor Big Blue Button (BBB) server is currently hosted at
<https://tor.meet.coop/>. Normally, someone will start a conference
and send you a special link for you to join. You should be able to
open that link in any web browser (including mobile phones) and join
the conference.

The web interface will ask you if you want to "join the audio" through
"Microphone" or "Listen only". You will typically want "Microphone"
unless you really never expect to talk via voice (would still be
possible), for example if your microphone is broken or if this is a
talk which you are just attending.

Then you will arrive at an "echo test": normally, you should hear
yourself talk. The echo test takes a while to load, you will see
"Connecting to the echo test..." for a few seconds. When the echo test
start, you will see a dialog that says:

> This is a private echo test. Speak a few words. Did you hear audio?

Typically, you will hear yourself speak with a slight delay, if so,
click "Yes", and then you will enter the conference. If not, click
"No" and check your audio settings. You might need to reload the web
page to make audio work again.

When you join the conference, you may be muted: click on the "crossed"
microphone at the bottom of the screen to unmute yourself. If you have
a poor audio setup and/or if your room is noisy, you should probably
mute yourself when not talking.

See below for tips on improving your audio setup.

## Sharing your camera

Once you are connected with a web browser, you can share your camera
by clicking the crossed camera icon in the bottom row. See below for
tips on improving your video setup.

## Sharing your screen or presentation

To share your screen, you must be a "presenter". A moderator
(indicated by a square in the user list on the left), can grant you
presenter rights. Once you have those privileges, you can enable
screen sharing with the right-most icon in the bottom row, which looks
like a black monitor.

Note that Firefox in Linux cannot share a specific monitor: only your
entire display, see [bug 1412333](https://bugzilla.mozilla.org/show_bug.cgi?id=1412333). Chromium on Linux does not have
that problem.

Also note that if you are sharing a presentation, it might be more
efficient to *upload* the presentation. Click on the "plus" ("+"),
leftmost icon in the bottom row. PDFs will give best results, but that
feature actually supports converting any "office" (Word, Excel, etc)
document.

Such presentations are actually whiteboards that you can draw on. A
moderator can also enable participants to collaboratively draw over it
as well, using the toolbar on the right.

The "plus" icon can also enable sharing external videos or conduct polls.

## Connecting with a phone

When you join a conference with a web browser, at the top of the chat
window, you should see a message that looks something like this:

> Dial in number is 123.456.7890.
> SIP dial in URI is 987654321@sip.ca.meet.coop.
> Confrence PIN is 0000000.

The "Dial in number" actually allows other participants to call in a
phone number (redacted as "123-456-7890" above) and then enter a
conference PIN (redacted as "0000000" above) to enter the call with
any plain old telephone or cellular phone. Users may need to unmute by
hitting the "zero" ("0" on the keypad) on their phone.

# How-to

## Hosting a conference

To host a conference in BBB, you need an account. Ask a BBB admin to
grant you one (see the [service list](service) to find one) if you do not
already have one. Then head to <https://tor.meet.coop/> and log
in. 

You should end up in your "Home room". It is fine to host ad-hoc
meetings there, but for regular meetings (say like your team
meetings), you may want to create a dedicated room.

Each room has its own settings where you can, for example, set a
special access code, allow recordings, mute users on join, etc. You
can also share a room with other users to empower them to have the
same privileges as you.

Once you have created the conference, you can copy-paste the link to
others to invite them.

## Breakout rooms

As a moderator, you also have the capacity of creating "breakout
rooms" which will send users in different rooms for a pre-determined
delay. This is useful for brainstorming sessions, but can be confusing
for users, so make sure to explain clearly what will happen
beforehand, and remind people before the timer expires. 

A common issue that occurs when breakout room finish is that users may
not automatically "rejoin" the audio, so they may need to click the
"phone" button again to rejoin the main conference.

## Improving your audio and video experience

Remote work can be hard: you simply don't have the same "presence" as
when you are physically in the same place. But we can help you get
there. 

[Ben S. Kuhn][] wrote this extraordinary article called "[How to make
video calls almost as good as face-to-face][]" and while a lot of its
advice is about video (which we do not use as much), the advice he
gives about audio is crucial, and should be followed.

[How to make video calls almost as good as face-to-face]: https://www.benkuhn.net/vc/
[Ben S. Kuhn]: https://www.benkuhn.net/

This section is strongly inspired by that excellent article, which we
recommend you read in its entirety anyways.

### Audio tips

Those tips are critical in having a good audio conversation
online. They apply whether or not you are using video of course, but
should be applied *first*, before you start going into a fancy setup.

All of this should cost less than 200$, and maybe as little as 50$.

Do:

 1. ensure a **quiet work environment**: find a quiet room, close the
    door, and/or schedule quiet times in your shared office for your
    meetings, if you can't have your own office

 2. if you have network issues, **connect to the network with cable**
    cable instead of WiFi, because the problem is [more likely to be
    flaky wifi][] than your uplink

[more likely to be flaky wifi]: https://www.benkuhn.net/wireless/

 3. buy **comfortable** headphones that **let you hear your own
    voice**, that is: normal headphones without noise reduction, also
    known as [open-back headphones][]

[open-back headphones]: https://www.soundguys.com/open-back-vs-closed-back-headphones-12179/

 4. use a headset mic -- e.g. [BoomPro][] (35$), [ModMic][] (50$) --
    which will sound better and pick up less noise (because closer to
    your mouth)

[ModMic]: https://antlionaudio.com/products/modmic-uni
[BoomPro]: https://www.sweetwater.com/store/detail/BoomProMic--v-moda-boompro-microphone-communication-mic-for-headphones

You can combine items 3 and 4 and get a USB headset with a boom
mic. Something as simple as the [Jabra EVOLVE 20 SE MS][] (65$)
should be good enough until you need professional audio.

[Jabra EVOLVE 20 SE MS]: https://www.jabra.com/business/office-headsets/jabra-evolve/jabra-evolve-20

Things to avoid:

 1. **avoid wireless headsets** because they introduce a *lot* of
    latency
 
 2. **avoid wifi** because it will introduce reliability and latency
    issues

Then, as Ben suggests:

> You can now leave yourself unmuted! If the other person also has
> headphones, you can also talk at the same time. Both of these will
> make your conversations flow better.

This idea apparently comes from [Matt Mullenweg][] -- Wordpress
founder -- who prominently featured the idea on his blog: "[Don't
mute, get a better headset][]".

[Don't mute, get a better headset]: https://ma.tt/2020/03/dont-mute-get-a-better-headset/
[Matt Mullenweg]: https://ma.tt/

### Video tips

Here are, directly from from [Ben's article][], notes specifically
about video conferencing. I split it up in a different section because
we mostly do *audio-only* meeting and rarely open our cameras.

[Ben's article]: https://www.benkuhn.net/vc/

So consider this advice purely optional, and mostly relevant if you
actually stream video of yourself online regularly.

> 6. (~$200) Get a second monitor for notes so that you can keep Zoom
>    full-screen on your main monitor. It’s easier to stay present if
>    you can always glance at people’s faces. (I use an iPad with
>    Sidecar for this; for a dedicated device, the right search term is
>    “portable monitor”. Also, if your meetings frequently involve
>    presentations or screensharing, consider getting a third monitor
>    too.)
>
> 7. ($0?) Arrange your lighting to cast lots of diffuse light on your
>    face, and move away any lights that shine directly into your
>    camera. Lighting makes a bigger difference to image quality than
>    what hardware you use!
>
> 8. (~$20-80 if you have a nice camera) Use your camera as a
>    webcam. There’s software for [Canon][], [Fujifilm][],
>    [Nikon][], and [Sony][] cameras. (You will want to be able to
>    plug your camera into a power source, which means you’ll probably
>    need a “dummy battery;” that’s what the cost is.)
>
> 9. (~$40 if you have a smartphone with a good camera) Use that as a
>    webcam via [Camo][].
>
> 10. (~$350) If you don’t own a nice camera but want one, you can get
>     a used entry-level mirrorless camera + lens + dummy battery +
>     boom arm. See [buying tips][].

[buying tips]: https://www.benkuhn.net/vc/#a-note-on-camera-buying
[Camo]: https://reincubate.com/camo/
[Sony]: https://support.d-imaging.sony.co.jp/app/webcam/en/
[Nikon]: https://downloadcenter.nikonimglib.com/en/download/sw/176.html
[Fujifilm]: https://fujifilm-x.com/en-us/support/download/software/x-webcam/
[Canon]: https://www.usa.canon.com/internet/portal/us/home/support/self-help-center/eos-webcam-utility

This section is more involved as well, so I figured it would be better
to prioritise the *audio* part (above), because it is more important
anyways.

Of the above tips, I found most useful to have a second monitor: it
helps me be distracted *less* during meetings, or at least it's easier
to notice when something is happening in the conference.

## Testing your audio

Big Blue Button actually enforces an echo test on connection, which
can be annoying (because it's slow, mainly), but it's important to
give it a shot, just to see if your mic works. It will also give you
an idea of the latency between you and the audio server, which, in
turn, will give you a good idea of the quality of the call and its
interactions.

But it's not as good as a real mic check. For that, you need to record
your voice and listen to it later, which an echo test is not great
for. There's a site called [miccheck.me][], [built with free
software][], which provides a client-side (in-browser) application to
do an echo test. But you can also use any recorder for this purpose,
for example [Audacity][] or any basic sound recorder.

[Audacity]: https://www.audacityteam.org/
[built with free software]: https://github.com/onetwothreebutter/mic-check
[miccheck.me]: https://www.miccheck.me/

You should test a few sentences with specific words that "pop" or
"hiss". Ben (see above) suggests using one of the [Harvard
sentences][] (see also [wikipedia][]).

[wikipedia]: https://en.wikipedia.org/wiki/Harvard_sentences
[Harvard sentences]: https://www.cs.columbia.edu/~hgs/audio/harvard.html

To quote Ben again:

> If those consonants sound bad, you might need a better windscreen,
> or to change how your mic is positioned. For instance, if you have a
> headset mic, you should position it just beside the corner of your
> mouth—not directly in front—so that you’re not breathing/spitting
> into it.

## Pager playbook

<!-- information about common errors from the monitoring system and -->
<!-- how to deal with them. this should be easy to follow: think of -->
<!-- your future self, in a stressful situation, tired and hungry. -->

## Disaster recovery

<!-- what to do if all goes to hell. e.g. restore from backups? -->
<!-- rebuild from scratch? not necessarily those procedures (e.g. see -->
<!-- "Installation" below but some pointers. -->

# Reference

## Installation

TPI is currently using [Big Blue Button][] hosted by [meet.coop][]
at <https://tor.meet.coop/> for regular meetings.

[meet.coop]: https://meet.coop/
[Big Blue Button]: https://bigbluebutton.org/

## SLA

N/A. Meet.coop has a [disclaimer][] that serves as a terms of service.

[disclaimer]: https://www.meet.coop/disclaimer/

## Design

N/A.

## Issues

There is no issue tracker specifically for this project, [File][] or
[search][] for issues in the [team issue tracker][search].

 [File]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/new
 [search]: https://gitlab.torproject.org/tpo/tpa/team/-/issues

Be warned that TPA does not manage this service and therefore is not
in a position to fix most issues related with this service. Big Blue
Button's [issue tracker is on GitHub][] and meet.coop has a
[forum][].

[forum]: https://forum.meet.coop/
[issue tracker is on GitHub]: https://github.com/bigbluebutton/bigbluebutton/issues

### Known issues

Those are the issues with Big Blue Button we are aware of:

 * mute button makes a sound when pressed
 * breakout rooms do not re-enable audio in main room when completed
 * has no global remote keyboard control (e.g. Mumble has a way to set
   a global keyboard shortcut that works regardless of the application
   in focus, for example to mute/unmute while doing a demo)

## Monitoring and testing

TPA does not monitor this instance.

## Logs and metrics

N/A. Meet.coop has a [privacy policy][].

[privacy policy]: https://www.meet.coop/privacy/

## Backups

N/A.

## Other documentation

 * [Meet.coop](https://www.meet.coop/):
   * [source code](https://git.coop/meet)
   * [forum](https://forum.meet.coop/)
 * [Big Blue Button](https://bigbluebutton.org/):
   * [source code](https://github.com/bigbluebutton/bigbluebutton/)
   * [issue tracker](https://github.com/bigbluebutton/bigbluebutton/issues)

# Discussion

## Overview

With the rise of the SARS-COV-2 pandemic, even Tor, which generally
works remotely, is affected because we were still having physical
meetings from time to time, and we'll have to find other ways to deal
with this. At the start of the COVID-19 pandemic -- or, more
precisely, when isolation measures became so severe that normal
in-person meetings became impossible -- Tor started looking into
deploying some sort of interactive, real-time, voice and ideally video
conferencing platform.

This was originally discussed in the context of internal team
operations, but actually became a requirement for a 3-year project in
Africa and Latin America. It's part of the 4th phase, to support for
partners online. Tor has been doing training in about 11 countries,
but has been trying to transition into partners on the ground, for
them to do the training. Then the pandemic started and orgs are moving
online for training. We reached out to partners to see how they're
doing it. Physical meetings are not going to happen. We have a year to
figure out what to do with the funder and partners. Two weeks ago gus
talked with trainers in brazil, tried jitsi which works well but
facing problems for trainings (cannot mute people, cannot share
presentations). They tried BBB and it's definitely better than Jitsi
for training as it's more like an online classroom.

Discussions surrounding this project started in [ticket 33700](https://bugs.torproject.org/33700) and
should continue there, with decisions and facts gathered in this wiki
page.

## Goals

### Must have

 * video/audio communication for a group of people of approx 2-10 people
 * specifically, work session for teams internal to TPI
 * also, training sessions for people *outside* of TPI
 * host partner organizations in a private area in our infrastructure
 * number of participants: 14 organisations with one training per month, max 4 per month, about 14-15 people per session, less than 20
 * chat fallback
 * have a mobile app 
 * allow people to call in by regular phone
 * a way for one person to mute themselves
 * long term maintenance costs covered

### Nice to have

 * Reliable video support. Video chat is nice, but most video chat
   systems usually require all participants to have video off
   otherwise the communication is sensibly lagged.
 * usable to host a Tor meeting, which means more load (because
   possibly > 20 people) and more tools (like slide sharing or
   whiteboarding)
 * multi-party lightning talks, with ways to "pass the mic" across
   different users (currently done with Streamyard and Youtube)
 * respecting our privacy, peer to peer encryption or at least
   encrypted with keys we control
 * free and open source software
 * tor support

### Non-goals

 * land a man on the moon

## Approvals required

 * grant approvers
 * TPI (vegas?)

The budget will be submitted for a grant proposal, which will be
approved by donors. But considering that it's unlikely such a platform
would stay unused within the team, the chosen tool should also be
approved by the TPI team as well. In fact, it would seem unreasonable
to deploy such a tool for external users without first testing it
ourselves.

## Timeline

 * april 2020: budget
 * early may 2020: proposal to funders
 * june 2020 - june 2021: fourth phase of the training project

## Proposed Solution

## Cost

Pessimistic estimates for the various platforms.

Each solution assumes it requires a dedicated server or virtual server
to be setup, included in the "initial setup". Virtual servers require
less work than physical servers to setup.

The actualy prices quoted from Hetzner but virtual servers would
probably be hosted in our infrastructure which might or might not
incur additional costs.

### Summary

| Platform        | One time  | Monthly        | Other                               |
| --------        | --------  | -------        | ----------------------------------- |
| Mumble          | 20 hours  | €13            | 2h/person + 100$/person for headset |
| Jitsi           | 74 hours  | €54 + 10 hours |                                     |
| Big Blue Button | 156 hours | €54 + 8 hours  |                                     |

### Caveats

 1. **Mumble is harder to use** and has proven to absolutely **require
    a headset** to function reliably
 2. it is assumed that **Jitsi and BBB** will have **similar
    hardware** requirements. this is based on the experience that BBB
    seems to scale better than Jitsi but since it has more features
    might require comparatively more resources
 3. BBB is marked as having a **lesser monthly cost** because their
    development cycle seems slower than Jitsi. that might be **too
    optimistic**: we do not actually know how reliable BBB will be in
    production. preliminary reports of BBB admins seem to say it's
    fairly stable and doesn't require much work after the complex
    install procedure
 4. BBB will take **much more time to setup**. it's more complex than
    Jitsi, but it also requires an Ubuntu, which we do not currently
    support in our infrastructure (and an old version too, so upgrade
    costs were counted in the setup)
 5. current TPA situation is that we will be **understaffed by 50%**
    starting on May 1st 2020, and by **75% for two months during the
    summary**. this project is **impossible to realize** if that
    situation is not fixed, and would still be **difficult to
    complete** with the previous staff availability.

A safe way to ensure funding for this project without threatening the
sability of the team would be to hire at least part time worker
especially for the project, which is 20 hours a month, indefinitely.

### Mumble

Assumed configuration

 * minimal Mumble server
 * no VoIP
 * no web configuration

One time costs:

 * initial setup: 4 hours
 * puppet programming: 6 hours
 * maintenance costs: near zero
 * **Total**: 10 hours doubled to 20 hours for safety

Recurring costs:

 * onboarding training: 2 hours per person
 * mandatory headset: 100$USD per person
 * [CPX31 virtual server](https://console.hetzner.cloud/): €13 per month

### Jitsi

Assumed configuration:

 * single server install on Debian
 * max 14 simultaneous users
 * dial-in capability

One time:

 * initial setup: 8 hours
 * Puppet one-time programming: 6 hours
 * Puppet Jigasi/VoIP integration: 6 hours
 * VoIP provider integration: 16 hours
 * **Total**: 36 hours, doubled to 72 hours for safety

Running costs:

 * Puppet maintenance: 1 hour per month
 * Jitsi maintenance: 4 hours per month
 * [AX51-NVMe physical server](https://www.hetzner.com/dedicated-rootserver/ax51-nvme): €54 per month
 * **Total**: 5 hours per month, doubled to 10 hours for safety, +€54
   per month

### Big Blue Button

Assumed configuration:

 * single server install on Ubuntu
 * max 30 simultaneous users
 * VoIP integration

One time fee:

 * initial setup: 30 hours
 * Ubuntu installer and auto-upgrade configuration: 8 hours
 * Puppet manifests Ubuntu port: 8 hours
 * VoIP provider integration: 8 hours
 * One month psychotherapy session for two sysadmins: 8 hours
 * Ubuntu 16 to 18 upgrade: 16 hours
 * **Total**: 78 hours, doubled to 156 hours for safety

Running costs:

 * BBB maintenance: 4 hours per month
 * [AX51-NVMe physical server](https://www.hetzner.com/dedicated-rootserver/ax51-nvme): €54 per month
 * **Total**: 4 hours per month, doubled to 8 hours for safety, +€54
   per month

## Alternatives considered

### mumble

#### features

 * audio-only
 * moderation
 * multiple rooms
 * native client for Linux, Windows, Mac, iOS, Android
 * [web interface](https://github.com/Johni0702/mumble-web) (usable only for "listening")
 * chat
 * [dial-in](https://github.com/slomkowski/mumsi), unmaintained, unstable

Lacks video. Possible alternatives for whiteboards and screensharing:

 * http://deadsimplewhiteboard.herokuapp.com/
 * https://awwapp.com/
 * https://www.webwhiteboard.com/
 * https://drawpile.net/
 * https://github.com/screego/server / https://app.screego.net/

#### installation

there are two different puppet modules to setup mumble:

 * https://github.com/voxpupuli/puppet-mumble
 * https://0xacab.org/riseup-puppet-recipes/mumble 

still need to be evaluated, but i'd be tempted to use the voxpupuli
module because they tend to be better tested and it's more recent

### jitsi

#### installation

ansible roles: https://code.immerda.ch/o/ansible-jitsi-meet/ https://github.com/UdelaRInterior/ansible-role-jitsi-meet

puppet module: https://gitlab.com/shared-puppet-modules-group/jitsimeet

there's also a docker container and (messy) debian packages

prometheus exporter: https://github.com/systemli/prometheus-jitsi-meet-exporter

Mayfirst is testing a [patch for simultaneous interpretation](https://current.workingdirectory.net/posts/2021/jitsi-and-language-justice/).

### Nextcloud Talk

systemli is using this ansible role to install coturn: https://github.com/systemli/ansible-role-coturn

### BBB

#### features

 * audio, video conferencing support
 * [accesssible](http://docs.bigbluebutton.org/support/faq.html#accessibility) with live closed captionning and support for screen readers
 * whiteboarding and "slideshow" mode (to show PDF presentations)
 * moderation tools
 * chat box
 * embedded etherpad
 * dial-in support with Freeswitch
 * should scale better than jitsi and NC, at least [according to their FAQ](http://docs.bigbluebutton.org/support/faq.html#how-many-simultaneous-users-can-bigbluebutton-support): "As a rule of thumb, if your BigBlueButton server meets the minimum requirements, the server should be able to support 150 simultaneous users, such as 3 simultaneous sessions of 50 users, 6 x 25, etc. We recommend no single sessions exceed one hundred (100) users."

i tested an instance setup by a fellow sysadmin and we had trouble after a while, even with two people, doing a screenshare. it's unclear what the cause of the problem was: maybe the server was overloaded. more testing required.

#### installation

[based on unofficial Debian packages](https://docs.bigbluebutton.org/2.2/install.html), requires Freeswitch for
dialin, which doesn't behave well under virtualization (so would need
a bare metal server). Requires Ubuntu 16.04, [packages are closed
source](https://github.com/bigbluebutton/bigbluebutton/issues/8978) (!), [doesn't support Debian](https://github.com/bigbluebutton/bigbluebutton/issues/8861) or [other](https://github.com/bigbluebutton/bigbluebutton/issues/8876) [distros](https://github.com/bigbluebutton/bigbluebutton/issues/8956)

anadahz setup BBB using a [ansible role to install BBB](https://github.com/n0emis/ansible-role-bigbluebutton).

### Rejected alternatives

This list of alternatives come from the [excellent First Look
Media](https://tech.firstlook.media/how-to-pick-a-video-conferencing-platform) procedure:

 * [Apple Facetime](https://support.apple.com/HT204380) - requires Apple products, limited to 32 people
   and multiple parties only works with the very latest hardware, but E2EE
 * [Cisco Webex](https://www.webex.com/) - non-opensource, paid, cannot be self-hosted, but E2EE
 * [Google Duo](https://duo.google.com/about/) - requires iOS, Android, or web client, non-free,
   limited to 12 participants, but E2EE
 * [Google Hangouts](https://hangouts.google.com/), only 10 people, [Google Meet](https://meet.google.com/) supports 250
   people with a paid subscription, both proprietary
 * [Jami](https://jami.net/) - unstable but free software and E2EE
 * [Keybase](https://keybase.io/) - chat only
 * [Signal](https://signal.org/) - chat only
 * [Vidyo](https://www.vidyo.com/) - paid service
 * [Zoom](https://zoom.us/) - paid service, serious server and client-side security
   issues, not E2EE, but very popular and fairly reliable

### Other alternatives

Those alternatives have not been explicitely rejected but are somewhat
out of scope, or have come up after the evaluation was performed:

 * [bbb-scale](https://gitlab.com/bbb-scale/bbb-scale) - scale Big
   Blue Button to thousands of users
 * [Boltstream](https://github.com/benwilber/boltstream) - similar to Owncast, RTMP, HLS, WebVTT sync, VOD
 * [Galene](https://galene.org/) - single-binary, somewhat minimalist, breakout groups,
   recordings, screen sharing, chat, stream from disk, authentication,
   20-40 participants for meetings, 400+ participants for lectures, no
   simulcasting, no federation
 * [Lightspeed](https://github.com/GRVYDEV/Project-Lightspeed) - realtime streaming
 * [Mediasoup](https://mediasoup.org/) - backend framework considered
   by BBB developers
 * [Medooze](http://medooze.com/) - backend framework considered
   by BBB developers
 * [OpenCast](https://opencast.org/) - for hosting classes, editing, less interactive
 * [OpenVidu](https://openvidu.io/) - a thing using the same backend
   as BBB
 * [Owncast](https://github.com/owncast/owncast) - free software Twitch replacement: streaming with
   storage
 * [Venueless](https://venueless.org/) - BSL, specialized in hosting conferences
 * [Voctomix](https://github.com/voc/voctomix) and [vogol](https://salsa.debian.org/debconf-video-team/vogol) are used by the Debian video team to
   stream conferences online. requires hosting and managing our own
   services, although Carl Karsten @ https://nextdayvideo.com/ can
   provide that paid service.
