From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [RFC] pop3: support `?limit=$NUM' parameter in mailbox name
Date: Fri, 15 Sep 2023 15:17:19 -0400 [thread overview]
Message-ID: <20230915-skittle-huff-36d60d@meerkat> (raw)
In-Reply-To: <20230913220326.M198766@dcvr>
On Wed, Sep 13, 2023 at 10:03:26PM +0000, Eric Wong wrote:
> > What if we move the uuid into the password field -- it seems it belongs there
> > anyway, as it's tied to the user cookie.
>
> I've thought about that, too; but it can get tricky since passwords
> aren't visible in most UIs. I've also seen some UIs (not POP3) which
> forbid copy+paste in password fields.
>
> Furthermore, if a user wants to migrate to a different POP3 client;
> carrying their UUID with them is easier when it's readable in the
> username. (I'm assuming users won't be bothered backup their UUID
> anywhere)
That makes sense.
> I'm open to supporting both ways; but I'm also not inclined to
> do so unless there's evidence of real-world POP3 clients being
> unable to handle the user names.
>
> Documenting both ways can be overwhelming to users.
Yes, let's keep it as-is -- I'll test the patches shortly and follow up with
details.
-K
next prev parent reply other threads:[~2023-09-15 19:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 21:08 pop3 usability thoughts Konstantin Ryabitsev
2023-09-12 22:40 ` [RFC] pop3: support `?limit=$NUM' parameter in mailbox name Eric Wong
2023-09-13 6:20 ` Eric Wong
2023-09-13 15:33 ` Konstantin Ryabitsev
2023-09-13 22:03 ` Eric Wong
2023-09-15 19:17 ` Konstantin Ryabitsev [this message]
2023-09-13 16:08 ` Konstantin Ryabitsev
2023-09-14 0:38 ` Eric Wong
2023-09-15 20:03 ` Konstantin Ryabitsev
2023-09-15 20:41 ` Eric Wong
2023-09-18 13:46 ` Konstantin Ryabitsev
2023-09-18 21:14 ` Eric Wong
2023-09-19 21:28 ` Konstantin Ryabitsev
2023-09-22 2:18 ` [PATCH] pop3: support initial_limit " Eric Wong
2023-09-22 18:02 ` Konstantin Ryabitsev
2023-09-22 18:38 ` Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230915-skittle-huff-36d60d@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).