jitsi_app_c0

Tree: 0715f85796

Author	SHA1	Message	Date
Дамян Минков	4075e5deb7	fix: Fix speakerstats reports.	4 years ago
damencho	e6cdeb31ff	feat: Optimizes speaker stats to skip occupants with 0 talk time. Skips adding focus user and skips sending an empty message. Keep sending participant info for those left the room, to keep existing behaviour.	4 years ago
Дамян Минков	9f65ae52f1	fix: Prosody modules - drop unused and duplicate code and drop chatty debug statements (#8027) * chore: Updates mod_smacks.lua version to latest. https://hg.prosody.im/prosody-modules/file/db75772afb28/mod_smacks/mod_smacks.lua * Drop unused modules. * Update docs. * Move utility functions away from domain mapper. * Remove some chatty debug log messages. * Drops not needed patch for mod_websocket.	5 years ago
emrah	da33d8a033	fix: speakerstats_component, attempt to index (a nil value)	5 years ago
Boris Grozev	76e1217439	ref: Make is_healthcheck_room more generic.	5 years ago
damencho	eea8fef044	Initial Lobby backend implementation.	5 years ago
Saúl Ibarra Corretgé	073fdc7b0e	sperakerstats: prevent access of nil object (#5112) If the dominant speaker leaves their object will be gone from the mapping.	5 years ago
damencho	b4be1bcd05	Adds some checks about async. There are modules that will not work with prosody 0.10 as they depend on util.async. Adds a safeguard and print error about it in the logs. And others that just do not work because of the muc module API that they use.	5 years ago
drimovecz	ffded8d82a	Drimovecz/speakerstats (#4851) * Correctly process speaker stats events when the conference contains a subdomain	6 years ago
drimovecz	6ecd150f75	Add context user on speaker stats	6 years ago
damencho	a5fc62b920	Updates correct loading and fix checking is dominant speaker.	6 years ago
damencho	380d9c75d1	Simplifies logic and renames a method.	6 years ago
damencho	7a09befd87	Updates time to be in ms and sends update of stats when user joins.	7 years ago
damencho	3b4037553a	Adds server-side speaker stats handling. Adds the component which receives the messages from client and a module which enabled on a virtual host will start advertising the component. When clients discover the component they will send message to the component with the name of the room where the dominant speaker event happen.	7 years ago

14 Commits (0715f85796150d79b10bf36d7dfe26f42adea0d1)