[Cialug] April Meeting Reminder--Virtual Only

Wed Apr 8 14:40:28 UTC 2020

Would someone (or someones) be willing to present on Jitsi for next month?

On Wed, Apr 8, 2020 at 12:49 AM Jeffrey Ollie <jeff at ocjtech.us> wrote:

> On Tue, Apr 7, 2020 at 10:12 PM Hakan E. Duran <ehakanduran at gmail.com>
> wrote:
>
> > I have done the same on my home server and was able to host a meeting
> > last weekend that included some participants from overseas countries. I
> > did not set up the SIP or streaming/recording module
>
>
> I set up the SIP bridge using voip.ms and eventually got it working. The
> main problem was that I hadn't discovered the config regeneration issue so
> I was fighting that plus I needed to experiment with the right SIP
> settings. It worked for the short tests I tried. Even as cheap as voip.ms
> is it still costs money so I probably won't keep SIP long term. Plus I
> don't really need it for what I want to do with it (video conference with
> friends and family).
>
> I haven't tried streaming a chat to YouTube. I might try it out just to see
> how it works but the kinds of chats I want this for (friends and family) I
> wouldn't want to stream to YouTube. The same goes for recording.
>
> One thing that would have been cool is using the transcription support.
> Unfortunately that requires streaming all of the audio to Google and using
> their cloud-based speech-to-text APIs. Kinda defeats the purpose of hosting
> your own chat server, but if the LUG uses Jitsi Meet for meetings from now
> on it could be worth it to make it easier for hearing impaired members to
> benefit from the meetings.
>
> The etherpad support is kind of cool. I'll probably leave that enabled
> although I don't expect to use it a whole lot. I can see using it every now
> and then, say if I want to video chat with family and we're planning a
> family vacation or something.
>
> and I did not
> > enable authorization for participants.
>
>
> I tested both internal and LDAP authentication and they worked without
> hitches. There's no way I'd leave something like this publically
> accessible. One thing about authentication, it's only for people that are
> creating/hosting chats. Once the chat has been created anyone that knows
> the link can join by default. The host can add a password that guests would
> need to join a chat.
>
> I'll probably stick with LDAP.
>
> However, LetsEncrypt certificate
> > support was enabled and allowed participants to join with their mobile
> > devices without problem.
>
>
> Yeah, the Let's Encrypt support worked well. Unfortunately it's limited to
> the HTTP verification method. As far as I know you can't use the DNS
> verification methods.
>
>
> > It performed pretty well in my opinion without
> > any major issues. One thing that we noticed was sound distortion and
> > quality drain after about 60-70 minute mark.
>
>
> I'd be curious to know if that's a browser problem or if the server has a
> memory leak somewhere that's causing that.
>
>
> > I confirm the oddity you
> > reported, which was also stated/admitted on the github page.
> >
>
> Hah, figures that I'd miss the big bold "IMPORTANT" stamp in front of the
> information on the GitHub page.
>
> Overall, I liked it quite a bit.
> >
>
> Yeah, it's a decent alternative to using commercial offerings.
>
>
> >
> > On 20/04/07 01:14PM, Jeffrey Ollie wrote:
> > > I've set up a jitsi meet instance on a DigitalOcean droplet. The
> cheapest
> > > droplet which gives you 1G RAM didn't look like it would be quite
> enough
> > > RAM (cpu seemed fine) so I bumped up to a 4G ram droplet. I haven't
> done
> > a
> > > lot with it yet to know if that'll be enough.
> > >
> > > Setting it up wasn't too hard with the docker compose configs at
> > > https://github.com/jitsi/docker-jitsi-meet
> > >
> > > One oddity that tripped me up for a while is that the Docker images
> will
> > > generate a set of config files the first time they boot up base on the
> > .env
> > > file, but they _won't_ overwrite an already existing config.
> > >
> > > On Fri, Apr 3, 2020 at 11:31 AM Dave Hala <dave at 58ghz.net> wrote:
> > >
> > > > I could look at doing some integration with it if it works good on a
> > > > windows desktop as well as on android and ios mobile devices.
> > > >
> > > >
> > > >
> > > > On Fri, Apr 3, 2020 at 11:27 AM L. V. Lammert <lvl at omnitec.net>
> wrote:
> > > >
> > > > > We've been using Jitsi here, .. had some problems initially when
> > hosting
> > > > > on meet.jit.si, but those went away when we spun up our own VPS to
> > host
> > > > > meetings - something you can NOT do with other services.
> > > > >
> > > > >         Lee
> > > > > _______________________________________________
> > > > > Cialug mailing list
> > > > > Cialug at cialug.org
> > > > > https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> > > > >
> > > >
> > > >
> > > > --
> > > > NIFCAP  -The Premier Client Intake System for Non-Profit
> Organizations.
> > > > https://www.osis.us
> > > > _______________________________________________
> > > > Cialug mailing list
> > > > Cialug at cialug.org
> > > > https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> > > >
> > >
> > >
> > > --
> > > Jeff Ollie
> > > The majestik møøse is one of the mäni interesting furry animals in
> > Sweden.
> > > _______________________________________________
> > > Cialug mailing list
> > > Cialug at cialug.org
> > > https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> > _______________________________________________
> > Cialug mailing list
> > Cialug at cialug.org
> > https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> >
>
>
> --
> Jeff Ollie
> The majestik møøse is one of the mäni interesting furry animals in Sweden.
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
>