From: Juliusz Chroboczek <jch@irif.fr> To: galene@lists.galene.org Subject: [Galene] Upcoming changes to Galène's protocol: user states Date: Tue, 23 Mar 2021 18:31:33 +0100 [thread overview] Message-ID: <87pmzpydxm.wl-jch@irif.fr> (raw) Dear all, I've just had a chat with Alain (Galène's UI guy), and we've come to the conclusion that we need some changes to the protocol. I thought I'd run them through you. First of all, the UI needs to distinguish between users of different categories -- ops against ordinary users, as well as perhaps have a distinguished "speaker" during seminars and lectures (who might or might not happen to be an op). Second, we need some way for a user to signal their state. The obvious case is the "hand up" or "in queue" state, where a user requests attention from the speaker. This could be shown as an icon next to the user in the user list, or perhaps the speaker could have a dedicated window with a list of users in queue. The user data structure already has a list of permissions (op, presenter, etc.). The first step would be to add a second list, known as "states", which is controlled by the user itself and is not interpreted by the server; the user themselves can change their states at any time. The user's permissions are not currently known to other users. The second step would be to extend the "user" message, which is used to populate the user list, with two new fields, "permissions" and "states", which indicate the permissions and states, respectively, of a user to all the other users. Whenever something changes, a new "user" message (of kind "change") would be sent to all users. User states would not be interpreted by the server (just as userMessages are not), which would allow extending the frontend without further modifications to the server. The first application would be hands up, but some frontends might want to add moods or traditional states (busy, away, etc.). I'm not sure if user polls can be shoehorned into that framework, and how. Are there any other usage scenarios that I'm missing? -- Juliusz
reply other threads:[~2021-03-23 17:31 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87pmzpydxm.wl-jch@irif.fr \ --to=jch@irif.fr \ --cc=galene@lists.galene.org \ --subject='Re: [Galene] Upcoming changes to Galène'\''s protocol: user states' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox