public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Technical Issues with yesterday's Video Conference
Date: Tue, 07 Dec 2021 12:15:28 +0000	[thread overview]
Message-ID: <5E2EC192-F3BD-4A43-A225-E532816BEC04@ipfire.org> (raw)
In-Reply-To: <0AB9204D-02B9-41D7-9D0F-B2BE89F7A344@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]

Hello Paul,

Logging in should now work for you.

Best,
-Michael

> On 7 Dec 2021, at 12:08, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
> 
> Hey Paul,
> 
> I am sorry, but you are currently not permitted to create a room.
> 
> I limited this to a smaller list of users, just because I wasn’t sure what could go wrong if people start abusing this.
> 
> I will make this available for your and email you back.
> 
> Best,
> -Michael
> 
>> On 7 Dec 2021, at 11:50, paul kairis <kairis(a)gmail.com> wrote:
>> 
>> I created a testroom, I'm the host, but when I login with my username (pavlos) and password that I use in people.ipfire.org, login fails.
>> 
>> Paul
>> 
>> On Tue, Dec 7, 2021 at 4:20 AM Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>> Hello,
>> 
>> I would like to apologise to the people who could not join the video call yesterday.
>> 
>> To make it short: I do not know why, but I think we seriously need to find out why this has happened.
>> 
>> We had a couple of people on the call who did not have any problems joining - even with multiple devices.
>> 
>> Then others could not see or hear a thing, which I would blame on the endpoint device, but Adolf tried multiple different ones and I do not believe that they are all suddenly broken at the same time.
>> 
>> Could you guys try to set up a video call with yourself and check if the problem persists?
>> 
>> You can just go to https://jitsi.ipfire.org and create a random room, then log in and hopefully you should at least see yourself. Joining from another browser tab or another device should work too.
>> 
>> If this fails, please let me know what you can find.
>> 
>> Best,
>> -Michael
> 


  reply	other threads:[~2021-12-07 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGGyJTrNoTpULH1g8vGNxHeJ2J4RC9atMUffVodCibn_tUgtdw@mail.gmail.com>
2021-12-07 12:08 ` Michael Tremer
2021-12-07 12:15   ` Michael Tremer [this message]
     [not found] <CAGGyJTq9T3cpRRogOQCnajrc-5pD3-nv7hnsBKTVUvfgVZvdUw@mail.gmail.com>
2021-12-07 12:26 ` Michael Tremer
2021-12-07 11:20 Michael Tremer
2021-12-07 12:58 ` Adolf Belka
2021-12-07 15:32   ` Michael Tremer
2021-12-07 16:38     ` Adolf Belka

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=5E2EC192-F3BD-4A43-A225-E532816BEC04@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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