[Galene] Galène issues

[Juliusz Chroboczek <jch@irif.fr>]

I have imported part of my notes into the Github issue tracker:

  https://github.com/jech/galene/issues

Here are the other known limitations, which I didn't make into issues
since they deserve further thought and discussion before I can make them
precise.

1. We're currently opening a new PeerConnection (PC) for every stream.
   This implies that we perform a new ICE negotiation for every stream,
   which increases latency at the beginning of a connection.

   We could in principle bundle multiple streams into a single PC, but
   that has other issues:

     - if a PC has streams in both directions, a complex handshaking
       protocol will be needed in order to avoid race conditions when one
       side clloses a connection while the other pushes a new stream
       through it;

     - it might cause issues with middleboxes, such as routers that
       perform some form of fair queueing;

     - if done carelessly, it causes SDP bloat, since SDP maintains an 'm'
       section even for tracks that have been removed.

2. The protocol needs cleaning up and being made more symmetric in
   preparation for server federation.

3. We need a user interface for operations such as /kick.  This is easy --
   just put a contextual menu under the user list.  Alain has a prototype
   in his branch (sfu-update at https://lab.nexedi.com/alain.takoudjou/sfu).
   Note that we need to manipulate users by id, not by username as in
   Alain's branch.

4. We need a user interface for private messages.  Not sure what it should
   look like, I don't think that either BBB or Zoom are particularly good
   examples.

5. Do we want to allow removing one's own chat messages?  Careful with
   security, usernames are easily spoofed in groups that don't have
   per-user passwords, only the id is secure.

-- Juliusz