Jitsi Meet #35

Closed
opened 2024-05-21 18:20:49 +02:00 by lukas · 4 comments
Owner

Explore the use of a signaling sever instead of relying on P2P transmission, which drastically decreases the experience as more than a few people join a call.

Explore the use of a [signaling sever](https://github.com/strukturag/nextcloud-spreed-signaling) instead of relying on P2P transmission, which drastically decreases the experience as more than a few people join a call.
lukas self-assigned this 2024-05-21 18:20:49 +02:00
lukas added this to the Issue Board project 2024-05-21 18:20:49 +02:00
lukas changed title from Nextcloud Talk High-Performance-Backend to Jitsi Meet 2024-05-23 12:30:45 +02:00
lukas removed the
Status
Need More Info
Service
Nextcloud
labels 2024-05-23 12:31:16 +02:00
Author
Owner

Migrating this issue to instead explore the use of a Jitsi server for the following reasons:

  • Jitsi is a very well-developed software
  • Jitsi is way more useful and configurable than Nextcloud Talk
  • Jitsi has good integration with Matrix
  • If Jitsi works out, we can keep Talk as a P2P solution, and Jitsi as a conference solution
Migrating this issue to instead explore the use of a Jitsi server for the following reasons: - Jitsi is a very well-developed software - Jitsi is way more useful and configurable than Nextcloud Talk - Jitsi has good integration with Matrix - If Jitsi works out, we can keep Talk as a P2P solution, and Jitsi as a conference solution
lukas added spent time 2024-05-23 12:32:59 +02:00
11 hours
lukas deleted spent time 2024-05-23 12:33:03 +02:00
- 11 hours
lukas added spent time 2024-05-23 12:33:22 +02:00
1 hour 33 minutes
Author
Owner

A development instance is available at https://meet.libre.moe

A development instance is available at https://meet.libre.moe
Author
Owner

Requesting review from @leon

Requesting review from @leon
Author
Owner

To-Do List

  • Customize configuration decided to use defaults for now
  • Extensive testing with multiple people
  • Explore IPv6 for Port 10000 requires custom networking setup in podman, currently not a target due to complexity and not being an issue
  • Add to backups
  • Add to Uptime Monitor
# To-Do List - [ ] <del>Customize configuration<del> *decided to use defaults for now* - [ ] Extensive testing with multiple people - [ ] <del>Explore IPv6 for Port 10000<del> *requires custom networking setup in podman, currently not a target due to complexity and not being an issue* - [x] Add to backups - [x] Add to Uptime Monitor
lukas closed this issue 2024-06-03 16:52:22 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Total Time Spent: 1 hour 33 minutes
lukas
1 hour 33 minutes
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: KomuSolutions/igot99issues#35
No description provided.