From: Frank Carmickle <frank@carmickle.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, galene@lists.galene.org
Subject: [Galene] Re: four other oft-requested features
Date: Fri, 30 Jul 2021 15:44:27 -0400 [thread overview]
Message-ID: <161BB31B-3D72-4E45-80A0-C6DBB64714CB@carmickle.com> (raw)
In-Reply-To: <CAA93jw753VjzwA1YAjYzhTmnX_27oCGcYe3637d3Gjoq=rVapw@mail.gmail.com>
I haven't had time to look at this, but I really would like to help this effort along. Has there been any more discussion on what work needs to happen?
Would it be okay if I just provided feedback?
--FC
> On Jul 18, 2021, at 6:44 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
> Let me rope in a friend that is totally blind to help on the spec.
> Frank, the galene crew. Galene crew, frank. Frank was adding a few
> html assistance features to galene when last we spoke.
>
> On Sun, Jul 18, 2021 at 3:17 PM Juliusz Chroboczek <jch@irif.fr> wrote:
>>
>>>> Does the following work for you?
>>>>
>>>> https://galene.org/speech.html
>>
>>> Open the pod bay doors, hal.
>>
>> I assume this means it works for you. So how do you envision the feature?
>
> Yes, you made me laugh with that url. Thx.
>
>> - Messages are read as they arrive, or when you click on a button?
>
> As they arrive but if at all possible panned to one side or waiting
> for a gap in conversation.
>
>> - What happens if a new message arrives before the previous one has
>> finished reading? The new message is queued, or the old message is
>> interrupted?
>
> queued.
>
>>
>> - How is the language of the message determined? Manually by the user?
>> In the group configuration?
>
> Heh. auto-translation to another language on the fly would be amazing...
>
> Not in the group.
>
> The senders language should probably be in the "locale" info per browser
> Same for the reciever's language (though less so)
>
>
>
>>
>> I'm quite willing to implement it, but I need to be assured that there's
>> someone actually using it to help me tune the UI.
>
> Frank?
>
>>
>> -- Juliusz
>
>
>
> --
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>
> Dave Täht CTO, TekLibre, LLC
next prev parent reply other threads:[~2021-07-30 19:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 1:41 [Galene] " Dave Taht
2021-07-16 11:53 ` [Galene] " Juliusz Chroboczek
2021-07-16 13:07 ` [Galene] Re: four other oft-requested features / forwarding control ibu ☉ radempa
2021-07-16 14:14 ` Juliusz Chroboczek
2021-07-27 22:03 ` [Galene] Re: four other oft-requested features Eliot Mack
2021-07-27 22:12 ` [Galene] Recording H.264 [was: four other oft-requested features] Juliusz Chroboczek
2021-07-27 23:26 ` [Galene] " Eliot Mack
2021-07-28 12:03 ` Juliusz Chroboczek
2021-07-16 12:16 ` [Galene] Re: four other oft-requested features Antonin Décimo
2021-07-16 12:57 ` Jeroen van Veen
2021-07-16 13:08 ` T H Panton
2021-07-16 18:32 ` Juliusz Chroboczek
2021-07-17 23:35 ` Dave Taht
2021-07-18 22:17 ` Juliusz Chroboczek
2021-07-18 22:44 ` Dave Taht
2021-07-30 19:44 ` Frank Carmickle [this message]
2021-07-31 0:36 ` Juliusz Chroboczek
2021-07-31 16:39 ` [Galene] Speech [was: four other oft-requested features] Juliusz Chroboczek
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: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161BB31B-3D72-4E45-80A0-C6DBB64714CB@carmickle.com \
--to=frank@carmickle.com \
--cc=dave.taht@gmail.com \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox