real life test next tuesday 21:00 berlin time (utc+1)
-
If you join, please add your city/country to your name (
luckow (berlin/germany)
). Some problems are based on latency. The city/country helps us identify these potential problems.FYI: The netcup data centre is located in Nuremberg (Germany). "My" ping is around 20ms
PING jitsi.luckow.org (213.109.163.122) 56(84) Bytes an Daten. 64 Bytes von my.zitronenblau.de (213.109.163.122): icmp_seq=1 ttl=55 Zeit=18.9 ms
-
@humptydumpty any modern browser should be ok
yes the app seems down
maybe he is doing maintenance -
@humptydumpty to be fair. I will wait for a 24/7 instance of jitsi on Cloudron until the LDAP settings work. I need my "shared" Cloudron instance for so many projects that I'm not ready to abandon it to the world. A reliable public instance for jitsi is https://meet.jit.si/ or https://meet.ffmuc.net/.
20 minutes before the test starts, I "fire up" the jitsi app. And yes: you only require a "modern" browser (in case you missed it: shame on you ) and ideally a headset.
-
Reminder: 52 minutes to go.
-
@timconsidine I'm fine with it. Maybe next time with a bit more planning. For today, we need load. Every attendee counts. Bots are welcome too
-
I could only be for a short time since I am driving to a meeting! But it worked well for the short time was around
-
So to me, it looks like a reliable first app package. IMHO, up to 15 or 20 participants should not have any relevant problems with network, RAM or CPU.
Thank you for taking part in this little experiment -
@luckow Sorry I couldn't join I'm just home now.
I'm curious to know the resources available for the jitsi server - CPU, RAM as configured in the cloudron UI.
My (very ad-hoc) testing so far has not been too successful, but I've not had a chance to dedicate time.
-
@BrutalBirdie Oh! Then I need to look again at things. Thanks.