From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: meta@public-inbox.org
Subject: Thoughts on search-based imap mailboxes
Date: Fri, 2 Oct 2020 10:34:44 -0400 [thread overview]
Message-ID: <20201002143444.itpfbhg75wqy3eva@chatter.i7.local> (raw)
Hello:
While discussing something else on the kernel.org users list, the
question of "virtual inbox folders" came up when talking about imap and
public-inbox. Here's how I imagine it could work in a way that doesn't
require any kind of real user management.
- any site visitor can create a saved search against any index, which
would be generated with a random name (e.g. guid4) and stored on the
server via a simple guid->(index, search terms) mapping
- if imap is enabled, any user can also create an imap "account" that
would also be a guid random string, perhaps with a random password as
well (or no password, since guid4 strings should suffice)
- users can freely associate saved searches with these accounts, perhaps
optionally allowing them to save them with aliases, such that the
record is:
user_guid->(saved_search_guid, alias)
- when logging into imap with an actual random account name, the
associated inboxes would be displayed instead of the general listing
- accounts and saved searches that were not accessed within $DAYS would
be automatically purged
What are your thoughts about this scheme? I like it because it respects
users' privacy, since we cannot map accounts to developers, and because
it doesn't require any kind of central identity gatekeeping. Anyone
setting up a public-inbox mirror can immediately start using this scheme
without needing to set up any kind of identity management backends.
-K
next reply other threads:[~2020-10-02 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 14:34 Konstantin Ryabitsev [this message]
2020-10-02 20:08 ` Thoughts on search-based imap mailboxes Eric Wong
2020-10-03 14:50 ` Konstantin Ryabitsev
2020-10-03 19:40 ` Eric Wong
2021-02-05 22:37 ` James Bottomley
2021-02-06 0:01 ` 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=20201002143444.itpfbhg75wqy3eva@chatter.i7.local \
--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).