Why do you want to re jigasi? Have you encountered any problems?

[daxiondi]

I'm very interested in this project, but I want to know why you want to use trust to re jigasi. Is there any problem? Can you share it?

[jbg]

Jigasi is great, and this is not intended to replace it. It's an alternative that can co-exist.

We're doing this for a few reasons:

• We've found that Jigasi uses a lot more resources than is really necessary to perform its task (particularly memory). This is a lot more lightweight.
• We want to build some apps using lib-gst-meet to help to make sure that lib-gst-meet is capable enough for common usage scenarios.
• We want to add features to Jigasi (like AWS transcribe support), but I don't enjoy writing Java or Kotlin, and we don't have any Java or Kotlin developers on the team, so it's easier to rewrite.

[daxiondi]

Thank you for your reply. I will pay attention to this warehouse for a long time. If possible, I will participate in the contribution. In the jitsi-meet ecosystem, I think you and your team have done a great job.