- From: Heather Vescent <heathervescent@gmail.com>
- Date: Thu, 28 May 2020 10:00:09 -0700
- To: "public-credentials@w3.org" <public-credentials@w3.org>
- Message-ID: <CA+C6qMyKLaeA4HgFg1erR0csemy1WGRkhY_TkjhG6YcouVUHeg@mail.gmail.com>
It seems that this discussion is focused on technical requirements, which, IMHO, misses the point of the originating request, which is the onerous technical hurdle of the current SIP set up. I'm hearing that the community would appreciate a platform that is reliably usable. Because otherwise, the technology is a hurdle to productive participation, which results in people dropping out. Yes, I would take the lesser technology solution if it enabled more, diverse participation. This results in a stronger community, increased participation which result in building more robust technology. That's why we're here right? To build/define/design new tech solutions? So, which meeting technology solution will best facilitate a diverse group of attendees? Not everyone is going to be happy with what we select, so we must select based on what enables the kind of participation we want in the community. More technical hurdles to get on a call will only allow people who are comfortable with that here. I'd personally appreciate seeing us relax some of the more ideological technical requirements to enable broader, more diverse participation. Those voices are gonna make our CCG tech dreams a reality faster if we have them here vs throwing up hurdles that push them away. Respectfully, -Heather On Thu, May 28, 2020 at 9:18 AM Serge Wroclawski <serge@wroclawski.org> wrote: > I must concur with TK. > > Jitsi can certainly do everything we've mentioned that Zoom can do, is > open source, self-hosted, isn't explicitly banned by so many institutions, > doesn't have the same concerning governmental associations as Zoom, and > like Zoom, can be tied in with a phone system so that phone callers can be > supported. > > The optics of using Zoom alone are troubling, and I think that as an > institution we need to keep that in mind, even if we are (sadly) willing to > overlook the serious security and political issues that have arisen around > Zoom. > > - Serge > > > On Thu, May 28, 2020 at 03:31:16PM +0000, Taylor Kendal wrote: > > I have experience with a self-hosted Jitsi instance. While the ux isn’t > as “clean” as Zoom, it certainly checks all the boxes and offers a lot more > admin control. > > > > Not that any of us need “one more platform” but Veertly may also be > worth exploring. https://veertly.com/ > > > > TK > > > > ________________________________ > > From: rhiaro <amy@rhiaro.co.uk> > > Sent: Thursday, May 28, 2020 8:54 AM > > To: public-credentials@w3.org > > Subject: Re: ditch voip/sip > > > > Also I've had good success with hosted jitsi - which is open source, and > > can be self-hosted - with medium-sized groups. Their hosted version > > should support 35 people well (with video, I presume more with audio) > > and I think if you self-host it and set it up right it supports a lot > > more (I haven't tried this yet though). Jitsi also has screensharing, > > chat and hand-raising features. I think paying a member of the group (or > > small company) to maintain a jitsi instance would be more inkeeping with > > the spirit of the CCG.. > > > > On 28.5.2020. 16:47, rhiaro wrote: > > > Can we *enable* SIP for zoom though (W3C zoom hasn't managed this yet) > > > for those of us who'd rather not install zoom (because privacy and > > > security problems etc, or just avoiding proprietary software in > general) > > > and don't have one of those old fashioned phonecall-making devices? :) > > > > > > On 28.5.2020. 15:58, Drummond Reed wrote: > > >> +1 as well. Zoom + dial-in capability for phone access + IRC for > > >> scribing works well. > > >> > > >> On Wed, May 27, 2020 at 2:17 PM John, Anil <anil.john@hq.dhs.gov > > >> <mailto:anil.john@hq.dhs.gov>> wrote: > > >> > > >> > Zoom offers a phone dial-in option as an alternative which > > >> hopefully would cover members in more restrictive IT environments? > > >> > > >> > > >> > > >> +1 > > >> > > >> > > >> > > >> Provided any presentation materials are shared, this is a very > > >> viable option. > > >> > > >> > > >> > > >> Best Regards, > > >> > > >> > > >> > > >> Anil > > >> > > >> > > >> > > >> > > >> > > >> *From:* Rouven Heck <rouven.heck@consensys.net > > >> <mailto:rouven.heck@consensys.net>> > > >> *Sent:* Wednesday, May 27, 2020 3:19 PM > > >> *To:* Wayne Chang <wyc@fastmail.fm <mailto:wyc@fastmail.fm>> > > >> *Cc:* Joe Andrieu <joe@legreq.com <mailto:joe@legreq.com>>; MXS > > >> Insights <mxsinsights@gmail.com <mailto:mxsinsights@gmail.com>>; > > >> Kim Hamilton <kimdhamilton@gmail.com > > >> <mailto:kimdhamilton@gmail.com>>; Kostas Karasavvas > > >> <kkarasavvas@gmail.com <mailto:kkarasavvas@gmail.com>>; Nikos > > >> Fotiou <fotiou@aueb.gr <mailto:fotiou@aueb.gr>>; W3C Credentials > > >> CG <public-credentials@w3.org <mailto:public-credentials@w3.org>> > > >> *Subject:* Re: ditch voip/sip > > >> > > >> > > >> > > >> *CAUTION: *This email originated from outside of DHS. DO NOT click > > >> links or open attachments unless you recognize and/or trust the > > >> sender. Contact your component SOC with questions or concerns. > > >> > > >> > > >> > > >> Zoom offers a phone dial-in option as an alternative which > > >> hopefully would cover members in more restrictive IT environments? > > >> > > >> > > >> > > >> I also struggled multiple times to join via SIP, so I would be > > >> happy with Zoom too. > > >> > > >> > > >> > > >> On Wed, May 27, 2020 at 9:17 PM Wayne Chang <wyc@fastmail.fm > > >> <mailto:wyc@fastmail.fm>> wrote: > > >> > > >> A Zoom SIP connector seems to available for a fee to allow > > >> those users to > > >> join: > https://support.zoom.us/hc/en-us/articles/201363273-Getting-Started-With-H-323-SIP-Room-Connector > > >> > > >> > > >> > > >> Also, note that it seems Zoom doesn't support chatbots within > > >> the live meeting chat > > >> ( > https://devforum.zoom.us/t/allow-chatbots-to-join-meeting-chats/8875), > > >> although we could still have parity with the join/part > > >> notifications we have in IRC today using the Meetings Events > > >> webhooks > > >> ( > https://marketplace.zoom.us/docs/api-reference/webhook-reference/meeting-events/participant-joined-meeting > ). > > >> So if we were to use Zoom, we may need to rewrite this > > >> integration and should keep all the chat and scribing within > > >> IRC for max accessibility. > > >> > > >> > > >> > > >> On Wed, May 27, 2020, at 3:07 PM, Joe Andrieu wrote: > > >> > > >> We also have the problem that many of our members, > > >> including federal employees, are restricted from running > > >> Zoom on corporate computers. > > >> > > >> > > >> > > >> So, while I do like the idea of a standard screen sharing > > >> solution, I'd lean towards something that doesn't isolate > > >> our members who have IT departments with a sensitivity to > > >> Zoom's privacy and security issues. > > >> > > >> > > >> > > >> -j > > >> > > >> > > >> > > >> On Wed, May 27, 2020, at 10:17 AM, MXS Insights wrote: > > >> > > >> Kim, you may also want to look at the > > >> auto-transcription capability. It is being used on > > >> the Secure Data Storage WG, and it has convinced the > > >> community there. > > >> > > >> > > >> > > >> Michael Shea > > >> > > >> > > >> > > >> On May 27, 2020, at 7:10 PM, Kim Hamilton > > >> <kimdhamilton@gmail.com > > >> <mailto:kimdhamilton@gmail..com>> wrote: > > >> > > >> > > >> > > >> Thank you so much Balázs. When we've discussed > > >> this in the past, we had a few concerns around > > >> switching (which I've managed to block out), but > > >> the big factor that stands out is cost. DIF's > > >> support would be a tremendous help. > > >> > > >> > > >> > > >> I think all of our other concerns would be > > >> addressed by doing zoom + irc (for > > >> queueing/minutes). As a bonus, zoom recordings are > > >> way easier than what we do now (which is the > > >> reason some recordings are still > to-be-backfilled). > > >> > > >> > > >> > > >> Chairs: we'll need to make sure we're not > > >> forgetting anything; let's discuss. > > >> > > >> > > >> > > >> > > >> > > >> On Wed, May 27, 2020 at 2:03 AM Kostas Karasavvas > > >> <kkarasavvas@gmail.com > > >> <mailto:kkarasavvas@gmail.com>> wrote: > > >> > > >> +1 > > >> > > >> > > >> > > >> On Wed, May 27, 2020 at 9:29 AM MXS Insights > > >> <mxsinsights@gmail.com > > >> <mailto:mxsinsights@gmail.com>> wrote: > > >> > > >> +1 > > >> > > >> > > >> > > >> Michael Shea > > >> > > >> > > >> > > >> > On May 26, 2020, at 5:50 PM, Nikos > > >> Fotiou <fotiou@aueb.gr > > >> <mailto:fotiou@aueb.gr>> wrote: > > >> > > >> > > > >> > > >> > Hi, > > >> > > >> > I would like to bring up again the > > >> voip/sip issue. At least in my case it is > > >> impossible to connect using sip and I > > >> always end up dialing in using skype. I am > > >> wondering why sip is still the used > > >> method, especially given that ZOOM is used > > >> for other calls, even in the same group > > >> (e.g., did-resolution). I read in the > > >> mailing list archives that one of the > > >> reasons is audio recording, but AFAICT the > > >> audio recordings from most of the last > > >> meetings are missing (e.g., > > >> > https://w3c-ccg.github.io/meetings/2020-05-19/audio.ogg > > >> > https://w3c-ccg.github.io/meetings/2020-04-21/audio.ogg > > >> > https://w3c-ccg.github.io/meetings/2020-04-07/audio.ogg > > >> and many others) > > >> > > >> > > > >> > > >> > Best, > > >> > > >> > Nikos > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> -- > > >> > > >> Konstantinos A. Karasavvas > > >> > > >> Software Architect, Blockchain Engineer, > > >> Researcher, Educator > > >> > > >> http://kkarasavvas.com/ > > >> > > >> > > >> > > >> -- > > >> > > >> Joe Andrieu, PMP > > >> joe@legreq.com > > >> <mailto:joe@legreq.com> > > >> > > >> LEGENDARY REQUIREMENTS > > >> +1(805)705-8651 > > >> > > >> Do what matters. > > >> http://legreq.com > > >> <http://www.legendaryrequirements.com> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > > > > -- Heather Vescent <http://www.heathervescent.com/> President, The Purple Tornado, Inc <https://thepurpletornado.com/> Author, A Comprehensive Guide to Self Sovereign Identity <https://ssiscoop.com/> Author, The Cyber Attack Survival Manual <http://amzn.to/2i2Jz5K> @heathervescent <https://twitter.com/heathervescent> | Film Futures <https://vimeo.com/heathervescent> | Medium <https://medium.com/@heathervescent/> | LinkedIn <https://www.linkedin.com/in/heathervescent/> | Future of Security Updates <https://app.convertkit.com/landing_pages/325779/>
Received on Thursday, 28 May 2020 17:00:35 UTC