# CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.7 6 messages from 2020-06-10 to 2020-06-23. Participants: Eric Wong, Denton Liu. Thread: https://gitlist.dev/t/53650 ## Eric Wong, 2020-06-10 18:41 Subject: CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.7 Message-ID: <20200610184147.GA1887@dcvr> URL: https://gitlist.dev/e/20200610184147.GA1887%40dcvr ``` Hey all, I've been busy with public-inbox work this year. I started working on a read-only IMAP/IMAPS server, and I expect kernel.org to eventually host a v2 copy, too; and hopefully other folks get interested in mirroring. For now, you can access git@vger archives through 8 IMAP mailboxes sliced into ~50K messages to not overload clients. They go from 0..7, with 7 being the most recent: imaps://public-inbox.org/INBOX.comp.version-control.git.0 imaps://public-inbox.org/INBOX.comp.version-control.git.1 imaps://public-inbox.org/INBOX.comp.version-control.git.2 imaps://public-inbox.org/INBOX.comp.version-control.git.3 imaps://public-inbox.org/INBOX.comp.version-control.git.4 imaps://public-inbox.org/INBOX.comp.version-control.git.5 imaps://public-inbox.org/INBOX.comp.version-control.git.6 imaps://public-inbox.org/INBOX.comp.version-control.git.7 When more messages show up, imaps://public-inbox.org/INBOX.comp.version-control.git.8 should exist. I've tested with mutt, offlineimap and mbsync (isync). It's not yet complete (when is software ever?), but it's a usable start, I think. Some more info about it over on meta@public-inbox.org: https://public-inbox.org/meta/20200609113442.GA16856@dcvr/ https://public-inbox.org/meta/20200610070519.18252-1-e@yhbt.net/ And maybe JMAP is coming, too... ``` ## Denton Liu, 2020-06-10 23:31 Subject: Re: CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.7 Message-ID: <20200610233127.GA51956@generichostname> URL: https://gitlist.dev/e/20200610233127.GA51956%40generichostname In-Reply-To: <20200610184147.GA1887@dcvr> ``` Hi Eric, On Wed, Jun 10, 2020 at 06:41:47PM +0000, Eric Wong wrote: > Hey all, I've been busy with public-inbox work this year. > I started working on a read-only IMAP/IMAPS server, and I expect > kernel.org to eventually host a v2 copy, too; and hopefully > other folks get interested in mirroring. > > For now, you can access git@vger archives through 8 IMAP > mailboxes sliced into ~50K messages to not overload clients. > They go from 0..7, with 7 being the most recent: > > imaps://public-inbox.org/INBOX.comp.version-control.git.0 > imaps://public-inbox.org/INBOX.comp.version-control.git.1 > imaps://public-inbox.org/INBOX.comp.version-control.git.2 > imaps://public-inbox.org/INBOX.comp.version-control.git.3 > imaps://public-inbox.org/INBOX.comp.version-control.git.4 > imaps://public-inbox.org/INBOX.comp.version-control.git.5 > imaps://public-inbox.org/INBOX.comp.version-control.git.6 > imaps://public-inbox.org/INBOX.comp.version-control.git.7 > > When more messages show up, > imaps://public-inbox.org/INBOX.comp.version-control.git.8 > should exist. > > I've tested with mutt, offlineimap and mbsync (isync). > > It's not yet complete (when is software ever?), but it's a > usable start, I think. Some more info about it over on > meta@public-inbox.org: > https://public-inbox.org/meta/20200609113442.GA16856@dcvr/ > https://public-inbox.org/meta/20200610070519.18252-1-e@yhbt.net/ > And maybe JMAP is coming, too... 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 ;) -Denton ``` ## Eric Wong, 2020-06-11 00:30 Subject: Re: CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.7 Message-ID: <20200611003036.GA5446@dcvr> URL: https://gitlist.dev/e/20200611003036.GA5446%40dcvr In-Reply-To: <20200610233127.GA51956@generichostname> ``` Denton Liu 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... ``` ## Eric Wong, 2020-06-16 07:08 Subject: Re: CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.7 Message-ID: <20200616070832.GA13965@dcvr> URL: https://gitlist.dev/e/20200616070832.GA13965%40dcvr In-Reply-To: <20200611003036.GA5446@dcvr> ``` Eric Wong wrote: > Denton Liu 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... ``` ## Denton Liu, 2020-06-16 13:19 Subject: Re: CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.7 Message-ID: <20200616131922.GA721186@generichostname> URL: https://gitlist.dev/e/20200616131922.GA721186%40generichostname In-Reply-To: <20200616070832.GA13965@dcvr> ``` Hi Eric, On Tue, Jun 16, 2020 at 07:08:32AM +0000, Eric Wong wrote: > Eric Wong wrote: > > 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/ Aha, I noticed last night when I was using it that it seemed much snappier! I can also confirm on my end that your patch works and it makes the experience much better. Thanks again! ``` ## Eric Wong, 2020-06-23 18:08 Subject: CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.8 Message-ID: <20200623180829.GA6852@dcvr> URL: https://gitlist.dev/e/20200623180829.GA6852%40dcvr In-Reply-To: <20200610184147.GA1887@dcvr> ``` +Cc: Christian for Git Rev News 64 Eric Wong wrote: > When more messages show up, > imaps://public-inbox.org/INBOX.comp.version-control.git.8 They've showed up, and .8 now exists, bringing to total up to 9. ```