Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Some poorly thought out feedback on git head
Date: Tue, 03 May 2022 22:07:00 +0200	[thread overview]
Message-ID: <87v8um753v.wl-jch@irif.fr> (raw)
In-Reply-To: <CAA93jw7KGGj6xG4nNB=T2kh1xjCYbyFxv3mte1aUwp4o0d5ZCA@mail.gmail.com>

Hi Dave,

As you note, we have some problems with Safari.

> a safari user had their self view freeze,

Yeah, Safari will randomly pause videos at weird times in order to save
battery.  I've caught many such places, but I must have missed some.
That's the main reason why there is a play button at the bottom of the
video, which you can click if autoplay is denied by the browser.

> an iphone user was unhappy about the iphone interface, in particular
> seeing a black box where the chat window could have been.

That's a new one.  We definitely need more reports from Apple users.

> If I let it go idle, several times I was logged out.

Galene sends keepalives after 55s at most, on the assumption that the
smallest NAT timeout it will encounter is 60s.  I can easily reduce the
timeout, let me know if you have a value to suggest.

> In an earlier test,  I'd ran a wireguard vpn (also with a tailscale),
> both under lte, and it blew up - in one case, video couldn't get
> through but voice could. I have not worked to figure out what actually
> went wrong, it could be anything from packet size to a routing or nat
> problem.

That's a known issue with WebRTC, unfortunately: the connectivity probing
is completely decoupled from the data plane, and uses small packets.  If
the probes get through but the packets don't, you get a blackhole.

As a workaround, you can try typing « /set forceRelay true » and hitting
reload.

-- Juliusz

      reply	other threads:[~2022-05-03 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 19:04 [Galene] " Dave Taht
2022-05-03 20:07 ` Juliusz Chroboczek [this message]

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.galene.org/postorius/lists/galene.lists.galene.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8um753v.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=dave.taht@gmail.com \
    --cc=galene@lists.galene.org \
    --subject='[Galene] Re: Some poorly thought out feedback on git head' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox