Inquiry about the Status and Progress of the Vortex Branch

[johnsnowdies]

Dear Maintainers,

In light of the recent blockings of Discord in Russia and Turkey, I’m sure you’ve experienced a surge of interest in your project, along with an influx of issues and requests on GitHub (including, unfortunately, some less constructive ones, for which I apologize). However, there are many developers who are genuinely interested and ready to contribute to the development of this project.

I noticed that the Vortex project has been marked as deprecated, with a link to the new branch (vortex). However, it seems that this new branch appears to be less up-to-date compared to the main branch, and there is some uncertainty about the status of its development.

I would like to kindly ask if there are any updates regarding the progress on the vortex branch and whether the code there is currently considered the most relevant. Is active development still ongoing? Additionally, is there a roadmap or any plans for the future of this branch that the community should be aware of?

Since this project is open-source under the GNU Affero General Public License, the community would love to contribute and assist in any way we can if there is an opportunity to do so. We believe that with some guidance or collaboration, we could help ensure the continued success and development of the project.

Please let us know how we might be able to assist. Your feedback and guidance would be greatly appreciated.

Thank you for your time and for considering our offer of support!

Best regards,
Sergei

[nz-razdor]

Hi, @insertish

I would like to help in the development of this module.

I looked at the new version, where API works via websocket, in the previous version it works via REST, and it looks like the new version is incompatible with the current API.

What do you think about updating the dependencies in the current master branch and continue development there, but based on the new webrtc-rs library? It looks more simple than upgrading api server to support websocket, anyway it can be done later when the main functionality will work on the old API.

[insertish]

We are rewriting this completely to use LiveKit, this repository will be archived and the code will live at revoltchat/backend.
revoltchat/backend#318
revoltchat/backend#313

[nz-razdor]

We are rewriting this completely to use LiveKit, this repository will be archived and the code will live at revoltchat/backend. revoltchat/backend#318 revoltchat/backend#313

Thanks, I'll take a look at it.
In any case, if you need help with development, I'd be happy to help.