From: "Gabriel Kerneis" <gabriel@kerneis.info>
To: galene@lists.galene.org
Subject: [Galene] Re: suggestion: "others" in config file, versus "anon" in web interface
Date: Sun, 03 Jan 2021 14:15:55 +0100 [thread overview]
Message-ID: <a6184ecc-6fcb-4de5-80bc-4d7c508f6d8e@www.fastmail.com> (raw)
In-Reply-To: <87pn2m8f9o.wl-jch@irif.fr>
On Sun, 3 Jan 2021, at 11:51, Juliusz Chroboczek wrote:
> >> A better name would be welcome, but "anonymous" is a bad choice -- an
> >> anonymous user is just one that has an empty username. This is controlled
> >> by the "allow-anonymous" field.
>
> > "muted" ?
Why muted? Can't an anonymous user speak like any other?
> Too close, it will lead to confusion. See, it's like "Juliusz" -- too
> close to a name in English, people tend to mis-spell it. On the other
> hand, nobody ever mis-spells "Chroboczek". (Except the administration of
> the University of Paris, but they're a completely different category.)
I have a hard time understanding the value proposition here, if users can pick arbitrary pseudonyms anyway. In the chat in particular, having distinct usernames to distinguish who is speaking (albeit anonymously) seems like a feature to me. What about not allowing empty usernames, but generating (distinct) pseudonyms automatically if left empty?
Jitsi uses "a jitsi user" (maybe with an added counter #1), which I don't like very much. Google uses animals (at least for user icons), which reminds me of Ubuntu codenames.
Gabriel
next prev parent reply other threads:[~2021-01-03 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 11:21 [Galene] " err404
2021-01-01 17:00 ` [Galene] " Juliusz Chroboczek
2021-01-01 17:10 ` err404
2021-01-02 13:24 ` Toke Høiland-Jørgensen
2021-01-03 10:51 ` Juliusz Chroboczek
2021-01-03 13:15 ` Gabriel Kerneis [this message]
2021-01-03 17:02 ` 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=a6184ecc-6fcb-4de5-80bc-4d7c508f6d8e@www.fastmail.com \
--to=gabriel@kerneis.info \
--cc=galene@lists.galene.org \
/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