git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Taylor Blau <me@ttaylorr.com>, Eric Wong <e@80x24.org>
Cc: Carmen Andoh <candoh@google.com>,
	git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: Git Inclusion Summit
Date: Tue, 28 Jul 2020 22:45:08 +0530	[thread overview]
Message-ID: <6b4b3f77-a479-4d7b-d7c2-e3e35e658ac7@gmail.com> (raw)
In-Reply-To: <20200728162528.GH87373@syl.lan>

On 28-07-2020 21:55, Taylor Blau wrote:
> On Tue, Jul 28, 2020 at 10:07:26AM +0000, Eric Wong wrote:
>>
>> Jitsi w/ audio-only certainly seems to be a step in the right
>> direction and would be more inclusive.
>>
>> Is there any speech-to-text transcription done for the hearing
>> (or extremely bandwidth) impaired?
> 
> It looks like such a thing exists:
> https://jitsi.org/blog/a-speech-to-text-prototype/.
> 

Yeah. A link with current information appears to be:

https://github.com/jitsi/jigasi#using-jigasi-to-transcribe-a-jitsi-meet-conference

>> It'd ideally go to #git on IRC (or something that doesn't
>> require a browser to trigger swap storms on old systems).
>>
>> Even for people with good hearing, acceptable audio quality for
>> speech seems tricky to get right, being dependent on mics,
>> bandwidth, codecs, background noise, speaker/earphone quality,
>> etc.
> 
> I haven't look hard enough to see if it supports redirecting its output
> to an IRC channel, but my guess is that it probably doesn't.

I believe you're right. From the link above:

> Currently Jigasi can send speech-to-text results to the chat of a
> Jitsi Meet room as either plain text or JSON. If it's send in JSON,
> Jitsi Meet will provide subtitles in the left corner of the video,
> while plain text will just be posted in the chat.

> In either
> case, hopefully disabling audio and video is possible within Jitsi's web
> UI, and you should be able to read or write in the chat as well as read
> the transcription.
> 

I think there's just one catch. The transcription as of now appears to
use Google Cloud speech-to-text API. Well, its Google. I'll let you make
your own inferences. In any case, it hopefully wouldn't be a concern for
people who _read_ the transcription.

-- 
Sivaraam

  reply	other threads:[~2020-07-28 17:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 19:30 Carmen Andoh
2020-07-23 20:59 ` Jonathan Nieder
2020-07-23 22:26   ` Junio C Hamano
2020-07-24 12:55     ` Carmen Andoh
2020-07-26  4:02 ` Eric Wong
2020-07-27 15:10   ` Taylor Blau
2020-07-28 10:07     ` Eric Wong
2020-07-28 16:25       ` Taylor Blau
2020-07-28 17:15         ` Kaartic Sivaraam [this message]
2020-07-29 17:00           ` 24 hours to respond with date/duration preferences for inclusion summit Carmen Andoh
2020-07-29 18:25             ` Junio C Hamano
2020-07-29 19:29               ` Carmen Andoh
2020-07-28 16:44       ` Git Inclusion Summit Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6b4b3f77-a479-4d7b-d7c2-e3e35e658ac7@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=candoh@google.com \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=me@ttaylorr.com \
    --subject='Re: Git Inclusion Summit' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).