@random_walkerIf Zoom cares to resurrect its reputation, it needs to do four things right away. 1. Stop acting like malware. Although the intent isn't malicious, it's a dangerous slippery slope that makes it harder for the OS to block actual malware and creates new security risks for users. (twitter.com/_/status/1245103123389169665)
[LewisCowles]> Instead, the company has TLS encryption in place. This is essentially what browsers use to secure HTTPS websites and it means that data is encrypted between users and Zoom’s servers. But that’s different from ‘end-to-end’ encryption which protects all content shared between users from the company providing the service.
ZegnatAs far as #indieweb-meta goes: I would maybe add a link to that extra piece of commentary on the wiki so it is clear what you are commenting on [LewisCowles]. As the rest of the wiki page does not seem to mention things like E2E.
sknebelwhat I've seen is people critizing that they said "end-to-end" when they only did transport encryption to their servers, so their servers had access to the data
[LewisCowles]> Zoom does use TLS encryption, the same standard that web browsers use to secure HTTPS websites. In practice, that means that data is encrypted between you and Zoom’s servers, similar to Gmail or Facebook content. But the term end-to-end encryption typically refers to protecting content between the users entirely with no company access at all,
[LewisCowles]> Zoom, however, denies that it’s misleading users. The company told _The Intercept_, “When we use the phrase ‘End to End’ in our other literature, it is in reference to the connection being encrypted from Zoom end point to Zoom end point,” and that “content is not decrypted as it transfers across the Zoom cloud.”
[LewisCowles]> Zoom is using WebRTC. Somewhat. With a data channel. To handle live video streams, with their previous WebSocket architecture as fallback. And not the peer connection itself.
[LewisCowles]are they asking for the video data to be encrypted as well as transported through an encrypted socket? If so isn't it worse to layer encryption like that?
sknebelend-to-end would mean that zooms servers can't decrypt the traffic. That IMHO does not make sense as a default for a video chat product, but as on opt-in thing would do probably
ZegnatAnd then it gets double confusing when you get more technical people reading it, because they have yet again a different expectation for what all the terms mean, haha.
ZegnatI feel like the problem is non-network people communicating with non-network people in multiple layers while Zoom themselves feel no need to clarify any of the terms they use.
sknebelI don't think they do anything peer-to-peer (it's of course cheaper server-load wise, but has lots of problems, as many of the other examples show), but use WebRTC (a technology designed to support peer-to-peer) between browser client and server for performance reasons
sknebelwhich I think is a sane choice, their marketing just shouldn't muddle that up (no personal opinion if they did or not, I didn't review the sources)
boffosocko.comedited /OPML (+235) "/* XSL (making an OPML file look like HTML) */ Hsiaoming Yang using XSL to create a human-readable RSS feed" (view diff)
[tantek]note that is the /likes page which is about displaying the set of likes on a post, rather than the /like page which is all about a like post itself
[tantek]I'm having a better and better experience with "Hangouts" (https://meet.google.com/) for video chats of <10 people and I'm wondering what people think of considering using that for HWC instead of Zoom (given all the recent Zoom concerns reported)
[tantek]I guess I'm saying I used to be frustrated by it, performance issues etc., and some combination of fixes in meet.google plus maybe fixes in Firefox have made it substantially better over the past few months
aaronpkif you're interested in using this, i recommend doing a test flow with two windows side by side to see what the experience is like both hosting and joining a meeting