zlacker

[return to "Zoom terms now allow training AI on user content with no opt out"]
1. _ddzr+6c[view] [source] 2023-08-06 13:51:36
>>isodev+(OP)
Thankfully nothing like this is in Jitsi Meet’s TOS: https://jitsi.org/meet-jit-si-terms-of-service/

It never ceases to amaze me how companies choose the worst software!

◧◩
2. jonas2+Wt[view] [source] 2023-08-06 15:32:18
>>_ddzr+6c
Section 4 of the Jitsi Meet ToS grants them similar rights. It's just with mushier language.

> You give 8×8 (and those we work with) a worldwide license to use, host, store, reproduce, modify, create derivative works..., communicate, publish, publicly perform, publicly display, and distribute such content solely for the limited purpose of operating and enabling the Service to work as intended for You and for no other purposes.

IANAL, but it seems like that would include training on your data as long as the model was used as part of their service.

Everyone who operates a video conferencing service will have some sort of clause like this in their ToS. Zoom is being more explicit, which is generally a good thing. If Jitsi wanted to be equally explicit, they could add something clarifying that this does not include training AI models.

◧◩◪
3. rapnie+cv[view] [source] 2023-08-06 15:38:44
>>jonas2+Wt
Self-hosting Jitsi is the better option. Or BigBlueButton, and there are more self-hosted open-source Zoom alternatives.
◧◩◪◨
4. samspe+ya1[view] [source] 2023-08-06 19:29:38
>>rapnie+cv
Do you happen to know of others by any chance. For self-hosted video call solutions, looks like Jitsi and BigBlueButton (BBB) are the only decent options out there.
◧◩◪◨⬒
5. esbeeb+WI1[view] [source] 2023-08-06 22:54:42
>>samspe+ya1
QOS (Quality-of-Service) rules might starve your traffic of bandwidth. Are you sure you have perfect "Net Neutrality" on your side?

You would be well advised to use services where the traffic travels through https on port 443 on the server (because it's been my experience that it tends to get pretty good QOS favorability). My own little rule of thumb: "you can connect to any port you want, so long as it's port 443 https." ;)

◧◩◪◨⬒⬓
6. David+HL1[view] [source] 2023-08-06 23:15:11
>>esbeeb+WI1
On the other hand, tls/443 is pretty undesirable for media delivery in videoconferencing because a) it's tcp-based and the required ACKs mean a big reduction in throughput and increase in latency, especially in the presence of packet loss, and b) most video services these days (and open source servers) use webrtc which encrypts the data in transit already--so the tls encryption is a waste of resources

Though tls/443 is usually still supported because it's most often allowed by even restrictive firewalls and networks

[go to top]