On Apr 05, 2020, Celejar wrote: > On Fri, 3 Apr 2020 21:11:33 -0400 > Dan Purgert <dan@djph.net> wrote: > > > On Apr 03, 2020, Celejar wrote: > > > On Fri, 3 Apr 2020 12:46:00 -0400 > > > Dan Purgert <dan@djph.net> wrote: > > > > > > > On Apr 03, 2020, Celejar wrote: > > > > > [...] > > > > > Fair enough - but has anyone looked into, say, Jitsi Meet's default > > > > > settings? Do they block non-hosts from screen sharing? > > > > > > > > IIRC, jit.si (their web-client) defaults to needing a passphrase to even > > > > get in. But I only ever took a cursory glance before "everyone(tm)" > > > > decided to use Zoom (i.e. good luck to me ever getting teh missus, etc. > > > > off that platform). > > > > > > I did a quick test run at their hosted instance, at meet.jit.si I > > > created a meeting (using one of their generated semi-random phrases for > > > the URL / ID) on one computer, and then logged on to the same url from > > > another computer. No passphrase was required, which is apparently the > > > same as what Zoom was doing. > > > > Oh, right - You have to click the "Add Password" button in the big popup > > that shows the dial-in information. It's pretty prominent on the > > screen, and you kind of have to make an effort to get rid of it (or at > > least I did - there wasn't much contrast between the 'x' and the rest of > > that popup). > > > > > > > > > On the other hand, I think some of what Jitsi has going for it is that > > > > it's somewhat decentralized -- if "my" server's settings are daft, it's > > > > *my* problem, not Jitsi's (same for any other service I run myself). > > > > > > Exactly - your hardware, your network. Under your control, but you need > > > to bring the bandwidth and horsepower. I'm a little skeptical as to how > > > well it would perform over my home internet connection (besides for the > > > fact that it would certainly violate the TOS of pretty much any > > > residential ISP service). > > > > It actually doesn't violate any ToS here (least not my ISP, and the > > previous two that I've had). Granted the previous ones (DSL and low-end > > cable) wouldn't have been able to host it. > > > > Current ISP is FTTH, so I've got bandwidth to spare. > > Well, you don't name your ISPs, but I'm pretty sure the big ones > generally forbid running servers (for anything beyond "personal" use) on > residential connections. E.g.: Oops, must have pulled them out on accident. Old-old -> cox Old -> Time Warner (now Spectrum; good thing I got off before their AUP went insane) Current -> AT&T (although i did have to call their tech support to open port 25, and authorize "if I run an open relay, I'm the one at fault" -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
Attachment:
signature.asc
Description: PGP signature