* Changed render mode to standard compliant and adjusted CSS accordantly.
* Fixed HTML errors, removed XHTML reminiscences and whitespace.
* Added doctype and fixed a few HTML errors.
* The input field speakerStatsSearch overflows the dialog box. Added missing box-sizing.
Co-authored-by: Bo Frederiksen <bo.frederiksen@semaphor.dk>
* feat: Adds room info http endpoint jwt protected.
Used from dialplan from jigasi for handling passwords in IVR.
* squash: Fixes comments.
* squash: nginx api/rom-info
* fix: Skips tenant checks when enableDomainVerification is false.
* squash: Drops duplicate code and supports multi-shards.
By adding room= parameter in query and tenant prefix for the api we add support for multi-shards setup.
* feat: Enable domain verification by default.
This is used when verifying room access with token_verification module.
* squash: Update docs.
* Refactor load-test into an object.
* Convert to class syntax.
* Bind member function callbacks.
* More binding and thisage.
* More thisage.
* More tweaks
* Rename numParticipants as remoteParticipants.
* Change back.
* Fix userLeft.
* Add members for event listeners, to be able to remove them.
* Add numClients parameter that allows multiple clients to be started.
* Clear clients array on unload.
* Add latency between starting clients.
* fix: Fixes Let's Encrypt script.
It fails when certbot is not installed and exits with an error without installing anything.
* squash: Fixes certbot command after install.
This introduces a variable which holds the path to the detected `certbot`
binary and reuses that to fix the inconsistency which arose from looking for
`certbot` but then later using the hardcoded path `/usr/bin/certbot` in
invocations. This broke snap installations of certbot.
Fixes: https://github.com/jitsi/jitsi-meet/issues/11072
Co-authored-by: Oliver Schneider <oliver@assarbad.net>
Fixes
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
* fix: Drops wrong x tag.
* fix: Generates correct join error for lobby.
We were adding lobbyroom element in a location that violates the rfc and xmpp errors.
We add now and the correct one and will drop the wrong node when all clients are updated.
https://datatracker.ietf.org/doc/html/draft-ietf-xmpp-3920bis#section-8.3.2
* squash: Add todo comment.
* squash: Updates namespace.
By the time the timer is fired the room maybe recreated (destroyed and created again) and we do not want to destroy it again. The timer was keeping a reference to the old room and is destroying it without notifying the future occupants(jicofo).
Drop save, as we do not need it before destroying, check lobby.
Same applies to tenant names as it applies to room names, as the
tenants/subdomains are prefixed to the room names in prosody.
Signed-off-by: Christoph Settgast <csett86@web.de>
rooms are created in prosody in their urlencoded form, eg täst
becomes t%c3%a4st@conference.jitsi.example.org
As local params = formdecode(query) contains an urldecode, we
need to reencode the room name so that the room can be found in
prosody.
Closes: #10525
Signed-off-by: Christoph Settgast <csett86@web.de>
Breakout rooms are just reserved UUIDs, they need not exist as actual MUCs,
until a participant joins. Thus, take this into account when checking if a
participant is in a room.
- implement breakout-rooms
- integrated into the participants panel
- managed by moderators
- moderators can send participants to breakout-rooms
- participants can join breakout rooms by themselve
- participants can leave breakout rooms anytime
Co-authored-by: Robert Pintilii <robert.pin9@gmail.com>
Co-authored-by: Saúl Ibarra Corretgé <saghul@jitsi.org>