Would it work with lib-jitsi-meet? In other words, would you jitsi be able to take care of the hosting while we develop a custom interface with the lib?
Yes! You are welcome to build your own UI with lib-jitsi-meet.
JaaS: The team that builds Jitsi can now also run it for you
101–110 of 120 posts
Re: JaaS: The team that builds Jitsi can now also run it for you
#102Looking for pricing, I get to this page: https://www.8x8.com/products/apis/video >We're charging on a Monthly Active User (MAU) >Pricing starts at $0.35/MAU and decreases based on volume. >An MAU is defined as a unique user who attended at least one meeting, with at least one other user, in the same month. To determine a unique user, we store an identifier on the device's local storage, and that will remain the same…
(Jitsi Dev here) Yes you are correct. Cookie delete is indeed something that would trigger a new user count. So far we haven't seen this happen but if you believe your users would be massively cleaning cookies, we are happy to have a conversation and find a work around for you.
FWIW, me and my team would likely be super into paying for a hosted Jitsi if there was another pricing structure. We run our own but keeping it running smoothly takes away dev energy. Counting usage like this just seems very ripe for abuse by anybody who wishes to harm the group.
Re: JaaS: The team that builds Jitsi can now also run it for you
#103Now that they have commercialized the project, I suspect a rebranding away from "Meet" is probably coming next. It is obviously confusingly similar to Google Meet.
Jitsi were using "meet" years before google, way back when Hangouts was still newish and quite good.
Re: JaaS: The team that builds Jitsi can now also run it for you
#104Earlier quoted context omitted.
This is great since selfhosted jitsi somehow developed into an IT support nightmare for us. Would be awesome to hear how they are doing the scaling. Our IT only offers jitsi only for max 10 ppl in a room which keeps us from using it at least in 50% of the cases. Also some users are reporting problems, so it would really be great to see a supported desktop app for all relevant platforms for those that struggle to get…
BigBlueButton is more suitable for larger conferences.
Oddly enough, we also used BigBlueButton for a while and really loved the additional features like the whiteboard but also had to drop it because we were doing more support for BBB than our core product...
Re: JaaS: The team that builds Jitsi can now also run it for you
#105Hey all, saghul from team Jitsi here. Didn't expect this to spread so fast, thanks everyone! Happy to answer any questions you may have!
We host music events where ~500-2000 people watch a shared stream, and some subset of those people break off into video chat rooms to hang out with each other.
We'd love to pay for JaaS to host the video room portion of events, however the MAU pricing model doesn't work well for events that only last a day or two. Is there any alternative pricing model that charges by the day or minute?
Re: JaaS: The team that builds Jitsi can now also run it for you
#106I tried to run a Jitsi server. It's a madness full of Docker impossible things to run and a very long and confusing configuration file. I wonder why can't these things be provided as binaries with a simple set of settings. Now they offer Jitsi as a service for free up to 25 users? That's great though. It should cover 99% of normal people use cases, so no one will use meet.jit.si anymore.
I don't know about others but I much prefer running a docker container than a random binary.
Re: JaaS: The team that builds Jitsi can now also run it for you
#107when will E2EE get out of Beta?
Re: JaaS: The team that builds Jitsi can now also run it for you
#108Looking for pricing, I get to this page: https://www.8x8.com/products/apis/video >We're charging on a Monthly Active User (MAU) >Pricing starts at $0.35/MAU and decreases based on volume. >An MAU is defined as a unique user who attended at least one meeting, with at least one other user, in the same month. To determine a unique user, we store an identifier on the device's local storage, and that will remain the same…
I would still like to see an answer to the questions above. In particular, does a user who connects on three devices count as three MAUs?
Sounds like it. But at 35cents / month, that doesn’t sound like a bad outcome.
Re: JaaS: The team that builds Jitsi can now also run it for you
#109Earlier quoted context omitted.
As a user, I think Google Meet probably has the most cpu-friendly default settings for screensharing. They limit the framerate to 5fps, and they're careful to use either the native size of the screen or half the native size (which avoids at least some expensive scaling code paths). This is hard/impossible to get right on every machine, because encoder implementations vary widely across all the hardware and operating…
Hey, thank you for the recommendation and detailed info! Sadly Google meet is empirically one of the worst one, even without screen sharing CPU hovers at ~60%, with screen sharing it's completely unusable. My use case is live coding sessions in education btw.
I'm always interested in data points, so thank you! If you don't mind, I'd love to hear what hardware/OS you're using. We have a lot of test devices, and it sounds like your particular setup is one that Google (and possibly we) aren't doing a good job factoring into our settings defaults/workarounds/special cases. So I think we maybe need another test device. :-)
Re: JaaS: The team that builds Jitsi can now also run it for you
#110Looking for pricing, I get to this page: https://www.8x8.com/products/apis/video >We're charging on a Monthly Active User (MAU) >Pricing starts at $0.35/MAU and decreases based on volume. >An MAU is defined as a unique user who attended at least one meeting, with at least one other user, in the same month. To determine a unique user, we store an identifier on the device's local storage, and that will remain the same…
Jitsi is open source, so you can look at the exact mechanics of their billing counter to answer your question:
It's all orchestrated from here: https://github.com/jitsi/jitsi-meet/blob/master/react/featur...
Which generates the MAU ID via:
react/features/billing-counter/functions.js:80
/* * Returns the stored billing id (or generates a new one if none is present). * * @returns {string} */
export function getBillingId() {
let billingId = jitsiLocalStorage.getItem(BILLING_ID);
if (!billingId) {
billingId = uuid.v4();
jitsiLocalStorage.setItem(BILLING_ID, billingId);
}
return billingId;
}