Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Jitsi Meet: open-source video conferencing

meet.jit.si

Post reply on HN
Print view View original

71–80 of 96 posts

Re: Jitsi Meet: open-source video conferencing

#71

Post by cycloptic »

dwohnitmok wrote: post #25
quadrangle wrote: post #24

Earlier quoted context omitted.

Copyright assignment lets the entity take full management of the copyright including license enforcement etc. The idea of assignment to FSF is not merely to guarantee to the world that the original copyright holder won't offer competing licenses or something.

Right, but my original question remains. How would the FSF allow the original copyright holder to claw back the copyright after assignment? That seems like it would be potentially incredibly disruptive (e.g. if a contributor decides several years after a lot of work has been built on top of the contributed code to claw back the rights), especially because as far as I'm aware there isn't a separate license you give th…

It's part of the agreement you sign with them. The agreements are not public AFAIK, you'll only see them when you contact someone to assign the copyright. Yes it would be inconvenient if someone did that, but that's additional incentive for the FSF to make sure they do the right thing.

Re: Jitsi Meet: open-source video conferencing

#72

Post by Arathorn »

est31 wrote: post #56
rnhmjoj wrote: post #47

Friendly reminder that meet.jit.si is not end-to-end encrypted. So, unless hosting your own instance, using the website or the videoconference integration in Riot means your conversation is routed through an Atlassian-owned server. See https://github.com/jitsi/jitsi-meet/issues/409#issuecomment-... .

Are there any E2EE alternatives to it?

https://github.com/matrix-org/matrix-doc/blob/matthew/msc235... is where things are at on the Matrix side for this.

As others have pointed out, we use jitsi.riot.im, which is provided by New Vector (the company behind Riot) rather than anything to do with Atlassian/Jitsi/8x8.

Re: Jitsi Meet: open-source video conferencing

#73

Post by saghul »

rnhmjoj wrote: post #47

Friendly reminder that meet.jit.si is not end-to-end encrypted. So, unless hosting your own instance, using the website or the videoconference integration in Riot means your conversation is routed through an Atlassian-owned server. See https://github.com/jitsi/jitsi-meet/issues/409#issuecomment-... .

Hey there, Jitsi dev here.

Yes, that is correct (except the Atlassian bit, we are owned by 8x8 now).

Currently WebRTC does not provide the necessary tools to make E2EE possible while still being able to use smart video routing techniques such as simulcast and SVC.

There is hope! In order to be able to have E2EE 2 things are needed:

* some metadata must be available without decrypting packets, this is (mostly?) available as RTP packet extensions, called "frame markings" * an API is necessary to be able to inject one's own encrypting engine in the WebRTC chain, Google is working on this API and hopefully it's available later in the year. Google is calling this "insertable streams": https://www.chromestatus.com/feature/6321945865879552

Happy to answer any questions!

Re: Jitsi Meet: open-source video conferencing

#74

Post by saghul »

speedplane wrote: post #39

In 2020, a company that provides a product for free without a standard business model will be met with skepticism: not just from investors, but from users. How is jit.si able to do this for free where many other companies charge? Are they monetizing user data? Or trying to upsell some parent company services? Is this an honest-for-goodness non-profit because someone was fed up with video conferencing? None of these a…

Hey there, Jitsi dev here. Great questions, let me try to clarify.

Jitsi is now owned by 8x8, which has a clear business model. We recently launched 8x8 Meetings, which is a rebranded Jitsi Meet with a few extra bells and whistles.

We (Jitsi) have remained Open Source while navigating through 2 acquisitions (Atlassian and 8x8) and being Open Source is in our DNA. Thus, remaining in this state was always a non-negotiable item during acquisition talks.

Re: Jitsi Meet: open-source video conferencing

#76

Post by saghul »

n_cusan wrote: post #31

We tried jitsi for a while and found it did not perform well for screen sharing in large groups (which we use extensively). We switched to whereby.com (former appear.in) which is not free for group meetings (used to be though) but is much more reliable. Creating new meeting rooms works the same way as in jitsi

Hey there, any chance you remember when you tested this? We have recently fixed a number of problems with screen-sharing indeed!

Re: Jitsi Meet: open-source video conferencing

#78

Post by piffey »

k3liutZu wrote: post #75

You can also use the 8x8 meeting experience (which is using the same underlying technology) free in the browser https://8x8.vc (Source: I work for 8x8)

Is this the same as talky.io (which I've used in the past and liked)? All the same underlying technology as Google Meet, right? WebRTC with some extra magics?

Re: Jitsi Meet: open-source video conferencing

#79

Post by neiljohnson »

rnhmjoj wrote: post #47

Friendly reminder that meet.jit.si is not end-to-end encrypted. So, unless hosting your own instance, using the website or the videoconference integration in Riot means your conversation is routed through an Atlassian-owned server. See https://github.com/jitsi/jitsi-meet/issues/409#issuecomment-... .

Worth noting that Riot can be configured to use any jitsi instance, the default option is jitsi.riot.im which is hosted by New Vector on behalf of the Matrix.org Foundation.

Re: Jitsi Meet: open-source video conferencing

#80

Post by emcho »

commoner wrote: post #57
est31 wrote: post #56

Earlier quoted context omitted.

Are there any E2EE alternatives to it?

Nextcloud Talk is end-to-end encrypted, but not as easy to set up as Jitsi Meet. https://nextcloud.com/talk https://github.com/nextcloud/spreed

To be accurate: no tool that relies on webrtc is end-to-end encrypted. So, no, it isn't. It is encrypted on the wire, just like the other tools mentioned here.
Post reply on HN