git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git Inclusion Summit

From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Date
Jul 28, 2020, 17:15 UTC
Message-ID
<6b4b3f77-a479-4d7b-d7c2-e3e35e658ac7@gmail.com>
In-Reply-To
<20200728162528.GH87373@syl.lan>
On 28-07-2020 21:55, Taylor Blau wrote:
Show 11 quoted lines
> 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
Show 10 quoted lines
>> 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.
Show 5 quoted lines
> 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
Previous: Taylor BlauNext: Carmen Andoh
Message 9 of 13 in “Git Inclusion Summit”
  1. Carmen AndohJul 23, 2020
  2. Jonathan NiederJul 23, 2020
  3. Junio C HamanoJul 23, 2020
  4. Carmen AndohJul 24, 2020
  5. Eric WongJul 26, 2020
  6. Taylor BlauJul 27, 2020
  7. Eric WongJul 28, 2020
  8. Taylor BlauJul 28, 2020
  9. Kaartic SivaraamJul 28, 2020
  10. 24 hours to respond with date/duration preferences for inclusion summitCarmen Andoh, Jul 29, 2020
  11. Junio C HamanoJul 29, 2020
  12. Carmen AndohJul 29, 2020
  13. Jeff KingJul 28, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.