Stuff that could make work on Emacs itself more smooth.

* Bug tracker
** Asynchronous client
It would be wonderful if ~debbugs-gnu~ and ~debbugs-gnu-search~ used
their own thread/process to wait & process the server's response,
instead of forcing me to twiddle my thumbs for minutes.
** Attachment management
Thanks to Bob Proulx, I learned that one can

1. send attachments to nnn-quiet@debbugs.gnu.org,
2. (for large attachments, wait for moderation,)
3. go to https://debbugs.gnu.org/nnn and grab the URLs for the
   attachments,
4. send a followup mentioning these URLs to nnn@debbugs.gnu.org.

When compared to simply attaching files to one's messages, this
ensures (1) only large attachments get moderated: reports and patches
keep flowing freely (2) mail clients do not stall while browsing
threads, since messages sent to -quiet are not forwarded to the
mailing list.

It'd be neat if Debbugs had a way to automate the -quiet attachment
trick, e.g.

- send some attachments to nnn-attach@debbugs.gnu.org,
- Debbugs then sends a mail to nnn@debbugs.gnu.org saying:
  #+begin_example
  John Doe <jdoe@gnu.org> attached:
  config.log (150 kB) <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=nnn;filename=config.log…>
  repro.sh   (400  B) <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=nnn;filename=repro.sh…>
  #+end_example

([[https://lists.gnu.org/archive/html/help-debbugs/2020-07/msg00004.html][help-debbugs thread]])
* Mailing lists
** Message IDs
*** Summary buffer → Message-ID
#+begin_src elisp
(kill-new (mail-header-message-id (gnus-summary-article-header)))
#+end_src
*** TODO Message-ID → HTTP archive
- <https://lists.gnu.org>:
  #+begin_example
  https://lists.gnu.org/archive/cgi-bin/namazu.cgi
      ?query=%2Bmessage-id:<$MESSAGE_ID>
      &submit=Search!
      &idxname=$LIST
  #+end_example
- public-inbox: trivial
*** TODO HTTP archive → Message-ID
- <https://lists.gnu.org>: cf. =X-Message-Id= comment in HTML
- public-inbox: cf. URL