user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Denton Liu <liu.denton@gmail.com>
Cc: git@vger.kernel.org, meta@public-inbox.org
Subject: Re: CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.7
Date: Tue, 16 Jun 2020 07:08:32 +0000	[thread overview]
Message-ID: <20200616070832.GA13965@dcvr> (raw)
In-Reply-To: <20200611003036.GA5446@dcvr>

Eric Wong <e@80x24.org> wrote:
> Denton Liu <liu.denton@gmail.com> wrote:
> > Exciting news! Since I'm not actually subscribed to the mailing list,
> > public-inbox has been integral in my workflow by letting me reply to
> > messages that I'm not CC'd on. The IMAP gateway is a great development.
> > 
> > I fetched your message via IMAP just now ;)
> 
> Hi Denton, great to know you appreciate it :)
> 
> It's still in the early stages and there still seems to be a
> problem where it still interacts badly with mutt's header cache.
> Maybe checking over the old HTTPS/NNTPS endpoints once in a
> while if things appear too quiet is a good idea while I shake
> out some bugs.
> 
> I'm dreading the cost of ~100K RAM/storage overhead per-client
> connection to support sequence numbers properly...

OK, that ought to be fixed and I found what seems to be an
acceptable solution w.r.t. server-side overhead:
https://public-inbox.org/meta/20200612234924.GA31809@dcvr/

I've also just deployed a recursive descent parser for which is
hopefully compliant with the way IMAP search queries are parsed:
https://public-inbox.org/meta/20200616050540.13357-3-e@yhbt.net/

One of the annoyances of read-only IMAP is MUAs (unlike
newsreaders) lack the ability to store status flags for
new/unread messages.  I've got some ideas to deal with that on
the client-side...

  reply	other threads:[~2020-06-16  7:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200610184147.GA1887@dcvr>
     [not found] ` <20200610233127.GA51956@generichostname>
2020-06-11  0:30   ` CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.7 Eric Wong
2020-06-16  7:08     ` Eric Wong [this message]
2020-06-16 13:19       ` Denton Liu

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=20200616070832.GA13965@dcvr \
    --to=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=liu.denton@gmail.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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