user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <>
To: Eric Wong <>
Subject: Re: Thoughts on search-based imap mailboxes
Date: Sat, 3 Oct 2020 10:50:06 -0400	[thread overview]
Message-ID: <20201003145006.wm5ehgwkhilmst73@chatter.i7.local> (raw)
In-Reply-To: <20201002200830.GA17908@dcvr>

On Fri, Oct 02, 2020 at 08:08:30PM +0000, Eric Wong wrote:
> Konstantin Ryabitsev <> wrote:
> > Hello:
> > 
> > While discussing something else on the users list, the 
> Btw, is this list public?

It's not, because it's supposed to be just for people with accounts on and for things like maintenance and service outage 
notifications. However, discussions routinely veer into various 
directions, as one would expect.

> A client-side tool is likely required anyways, I'm thinking
> having saved search functionality in a local tool writing to
> Maildir/mbox might be the best way forward as w.r.t. scalability
> and offline access (and reading + saving flags from the
> Maildir/mbox).
> External/detached index I'm working on for global search will
> also be appropriate for client-side tooling, I think, as it's
> being designed with non-public-inbox data sources in mind, too.

Instead of a "client-side" can it just be an intermediary tool that can 
run either on the client, or on any other piece of infrastructure? The 
main reason I'm interested in that is because several people I know use 
very thin clients for their work (chromebooks) and I would like to offer 
them this service as a perk of instead of forcing them to set 
it up and maintain on their own.


  reply	other threads:[~2020-10-03 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 14:34 Thoughts on search-based imap mailboxes Konstantin Ryabitsev
2020-10-02 20:08 ` Eric Wong
2020-10-03 14:50   ` Konstantin Ryabitsev [this message]
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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201003145006.wm5ehgwkhilmst73@chatter.i7.local \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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).