From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: meta@public-inbox.org
Subject: pop3 usability thoughts
Date: Tue, 12 Sep 2023 17:08:00 -0400 [thread overview]
Message-ID: <20230912-impart-swinger-4c2434@meerkat> (raw)
Hello:
I've been playing around with pop3, and I'm wondering if we can improve its
usability by adding a "last NNN messages" pseudo-folder. Currently, if someone
wants to access the git mailing list archive via pop3, they have to do the
following:
- know that the username should be $(uuidgen)@org.kernel.vger.git.1 (the
default username would access slice 0, right? Or is it the last 50,000
messages?)
- wait for their client to retrieve tens of thousands of unread messages on
first access
- if the remote archive rolls over to the next slice, they have to edit their
account info to get new messages (unless I'm wrong about #1)
Perhaps the default could be slightly different:
- $(uuidgen)@org.kernel.vger.git would start with an empty view (or something
like the last 10 messages)
- it would only get any new messages added to the archive
I think this would be a friendlier experience, but not sure how difficult it
would be to implement. I'm also not 100% sure all my assumptions are correct,
so please feel free to correct me.
Best wishes,
-K
next reply other threads:[~2023-09-12 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 21:08 Konstantin Ryabitsev [this message]
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
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=20230912-impart-swinger-4c2434@meerkat \
--to=konstantin@linuxfoundation.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).