Nextcloud App for BigBlueButton integration

You are never unobserved :joy:

It’s a bit sad that we have now two applications for the same purpose, but I was not aware of that talk fork. Maybe we can cooperate, see

I’m currently preparing the first release and I think it will be published in the next hour. Would be great if we could have only one bbb app for Nextcloud.


Very cool. Again! It is awesome to have BBB or maybe Jitsi integration in Nextcloud. This can be alternatives to Nextcloud Talk. No problem here. But this need to be separate apps with separate names and IDs. Just forking Talk and patching BBB support in is not cool and not supportable. So as long as this are separate apps that don’t collide then all is awesome. As a check. It should be possible to install Nextcloud Talk and this other BBB/Jitis integration apps in parallel without PHP/JS Code conflicts or UI and Usability issues. Thanks everyone :slight_smile:


FYI: First version of (standalone) BBB integration released:

If you like to contribute and enhance this integration, please open an issue or pull request. I’m also happy to add more people to the repository.

The following things are on the roadmap for the next release:

  • translation (#2)
  • own file share point (currently the app is creating a share with a validity of one day) (#1)
  • Nicer join page (room name and so on)

There is a new category for this app for further discussions:

1 Like

Agreed, the intent was never to continue having the same name forever. Just a first step.
We’ll be releasing it to the store soon.

1 Like

very impressive :slight_smile:

I need the tuto for bbb integration with nextcloud

We tried to make changes to our fork so it is independent from NC Talk and hit roadblocks
The core of NC has hooks for Talk (i.e. spreed)

I don’t see anyone wanting to install multiple conferencing systems. So having Talk being installed with something else is not just realistic. And Talk has some cool features and integrations with files and calendar.

To be honest, a better alternative to all that we have a single NC Talk which supports both the internal signalling server and BBB / Jitsi. We already did the heavy-lifting for BBB. Can we just work with the developers of Talk and have multiple options for conferencing?

That should be the ideal option instead of this proliferation of conflicting apps.


I also think it would be more elegant if there was a selection in Talk: with BBB / Jitisi as an option.


You are definitely right. There must be a way to integrate Jitsi, BBB and may be others (open-source!) together with the actually foreseen, costly, signaling server connections.


:wave: your definitely right!

1 Like

May be such a bot could be a solution too?

1 Like

Oh my god, a working videoconference integration within Nextcloud would be just awesome. I really think it should be within Nextcloud Talk, since it’s just very good for chat and this functionality would perfectly fit in the gap of not be able to videoconference and the “not reinventing the wheel” idea of nextcloud.


:+1: I agree

Great. Just to be clear. When I mentioned that is should be possible to install Talk and your app in parallel then I didn´t want to suggest that this makes sense for users. But it´s a good test that the code and namespaces of the apps don´t collide. Because this would be bad coding style and dangerous. If this is all fine then I suggest you should publish it at to get more feedback from users.

Are you still planning to publish your app in the App Store?
I would be very happy!

1 Like

Sorry for delay.

Now that the server code is released, I am not sure we need this effort anymore. I am thinking of shelving it.

But one thing is for sure, the community having started developing alternatives to Talk, has put pressure to open source the underlying server. So it is a success as we are all much better off now.

1 Like

i know that it has been pretty much work 4 u so it would be a real pity if you would shelf it…
why not coming up with a v1 and then give it away?



The challenge is that the code (especially PHP) makes use of the original Talk namespace. It would require a substantial amount of work to get it ready for the apps store (to avoid namespace conflicts).

It is a cool effort, but I only see a handful of people really interested.

i guess there are a lot interested… but not capable of doing the work.

and of course that’s a task that needs to be done.
but anyways… putting it away can’t be the solution… maybe if you’d give it out to the world “as it is” with some comments what would need to be done before releasing it officially?

1 Like