Edgeryders test customers for Jitsi servers

I have never been in a single Jitsi call that deserved the name. Mostly I could barely understand anything.

Can he offer a video conferencing environment that we can test out with 15 people without setup efforts? I would not want to waste a day of setup work to find out it just does not work :stuck_out_tongue:

1 Like

Were these calls on dedicated servers or the free Jitsi Meet servers?

Yes, he is offering to set it up without any fees for us to test before paying anything. I guess we can do that first without going through the authentication with Discourse steps.

1 Like

It sounds to me more that we’d have to work for a day to get something working? That’s what I want to avoid. It also sounds like he’s still testing out the best way to configure a Jitsi server and is rather at the beginning of offering this as a product? That’s no deal-breaker, but … I got so annoyed with Jitsi that the first thing I need to see now is that it can be used to make a call.

(And I don’t know if the Jitsi “calls” I experienced were on Jitsi Meet or not … if the software is not able to detect bandwidth limitations and take corrective measures, there’s probably something missing in the software …)

No, I don’t think we need to do much. I think he will set it up and we just bring people and try it out. At worst, the time we waste may be trying out having one of our community calls break down, and we can always have a Zoom call as a backup.

But I only want to take the offer if we are in fact ready to pay for it in case we like it. In that case, it would require work on our end for the authentication through Discourse.

Would be happy to pay for open source infrastructure that works. The solution Owen is working on is as little open source as Zoom when it comes to the actual video component from daily.co.

If the initial call is promising, I’d be fine with signing up for a month and testing further. If it works, Owen can hopefully exchange the daily.co component with a Jitsi component, and we integrate the Discourse authentication in that way.

In other words, I’d not want to work on the Discourse integration until our first month of more extensive tests is over.

3 Likes
  • To schedule and invite to a call
  • Securely protect a call and only invite certain people
  • Be sure that the call is end not listened in on

As of the latest update, these are no longer missing features… You can create a call by referencing the id of the call topic, for example: https://now.edgeryders.eu/call/12876

This will only allow a user to join the call at the scheduled time, and only for the users listed in the RSVP. You can also limit access by discourse groups.

For the other two points, muting and kicking out participants is very easy to implement with the Daily.co API. I haven’t been able to test it with 20+ people but from my experience with it, the quality and latency is as good or better than any other service I have tested.

This isn’t to say another solution wouldn’t also work - but I would consider carefully where our resources should be spent if we have something working already…

I think the shortcomings you listed are less related to the API we are using, as they are to UI features that can be implemented… but there isn’t much sense in implementing them if we’re not sure which solution to go with.

From what I read about Jitsi, the benefits would be that it is open source, which I understand aligns better with the core values (but then again we are still using services like YouTube and Mailchimp, which are proprietary…). But the downside would mean running an extra server (just talked to @matthias about how we would like to avoid this), maintenance and associated costs - for something that does one thing.

The admin interface would also be an extra level of UI, arbitrarily disconnected from our platform - while the current system relies quite nicely on topics on the platform - that are open and editable.

This isn’t merely to play devil’s advocate (or push us for using daily.co - of which I own no stock :slight_smile: ), but just to point out some things that should be considered before jumping into another pond…

/cc @nadia @hugi

3 Likes

So I have been running Jitsi Meet servers for some time. The test part is where you would need to configure your platform to use the JWT plugin for auth. It should be mainly an issue of coordinating the settings.

Jitsi meet servers are in the US, and the videobridge routes all data, so that may be why Jitsi Meet is not eh best in EU. I have an instance running in NL if you wan to test?
:Ptr

You could try BigBlueButton - I was in a call with 10 ppl last Saturday that worked quite well. It’s meant to be for online classes so probably works for even more people, with some caveats for distance etc.

1 Like

Here is the discourse plugin: https://github.com/discourse/discourse-jwt

With that and a shared secret Meet can auth users from dicourse.

1 Like

Worried this could be getting more complicated than necessary…

I suggest we test it with an already running instance (maybe the one that @notme mentioned (thanks :slight_smile: ) and see if there are any real advantages to using it over what we have.

1 Like

Not sure if the bandwidth will last on the current one, if you want to test for a month?

For a full month of testing I can build a server for you. I can handle everything if you cover the cost (50€ for dual core). We can also try the JWT auth, as it only requires config on my end… If you can get JWT token auth to work on your side.

What would be a good date for the free one day test? I’ll invite others too so we can stress test the server. We can combine testing capacity if the time is suitable for all.

I think @hugi will coordinate the test day since he proposed the migration to Jitsi.

Would we have to install the discouse-jwt plugin already for the test or not? It would be kinda ok to do so, but the less work to see a demo of Jitsi with 20 people, the better. After a successful demo, we’ll be happy to invest some time into integration of course.

@MariaEuler, @nadia, @noemi
Do we have any community calls in the coming week that we could try this on? It would be interesting to get some people to do the first half of the call on @owen’s setup and then try Jitsi, so we can compare.

1 Like

How many people would you need to make it a vaiable test?

I think 20 would be great, but I think we could pull some more people in for just testing if they can just join the call an keep working like normal, no?

Was thinking asking the people from the open source call tomorrow evening to test it out. Could be a programm point there in itself. however, we would need to try to get some more people in there.

@notme, could it be ready to test tomorrow evening?

If you are speaking about jitsi (that is how I understood Maria in another thread), be aware that besides some server configuration, a single non-chromium-browser-user can potentially ruin the experience (also, for everybody else!) at the moment. I dont want to go into details here.
Point is: if you want to have a pleasant experience and rule out some weirdness, have your users use chromium (not safari, not edge, not firefox, not opera). Its a tough hit, because Firefox is kind of the only contender left in the browser-market; the jitsi-Team is working on it - but compatibility will not arrive tomorrow - I guess it will take weeks or months.
Chrome of course would work as well (Chromium is Google Chrome minus some of the tell-google-exactly-what-i-do-functionality).

2 Likes

Thank you for that insight :slight_smile: