user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: Re: brain dump detached/external index so far...
Date: Mon, 14 Sep 2020 20:55:46 +0000	[thread overview]
Message-ID: <20200914205546.GA28639@dcvr> (raw)
In-Reply-To: <20200914160114.kdwed3rkb52ibal4@chatter.i7.local>

Konstantin Ryabitsev <> wrote:
> I think several virtual inboxes makes more sense than always one global 
> search, as people may want to search something like "all Linux kernel 
> discussions" or "all gcc/compiler discussions". There could be different 
> frontends to indicate which search is running -- e.g.  
> "" vs. "".

It might be better to have one big index, still.  Groups can be
Xapian terms which are defined/redefined as-needed for filtering.
It would be helpful when compiler bugs are found in the course of
kernel development.

> As an off-side grumbling, we found out that AWS SES (their email 
> processing service) will force-rewrite all message IDs without any 
> option to prevent this. So, a single message with multiple recipients 
> will arrive with a unique Message-ID to each one of them.
> This is so broken, it blows my mind, but AWS doesn't care to fix it.

Eeeep.  I wonder if there's some benefit for Amazon in doing this...
I can understand why centralized communications providers
would Embrace, Extend, Extinguish email; but I didn't think
they'd have anything to gain by making email worse.
(I'm still anti-monopolist, anyways)

      reply	other threads:[~2020-09-14 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13  6:55 Eric Wong
2020-09-14 16:01 ` Konstantin Ryabitsev
2020-09-14 20:55   ` Eric Wong [this message]

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=20200914205546.GA28639@dcvr \ \ \
    --subject='Re: brain dump detached/external index so far...' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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