user/dev discussion of public-inbox itself
 help / color / Atom feed
From: "Nicolás Ojeda Bär" <>
To: Eric Wong <>
Subject: Re: public-inbox-httpd feature request: sort oldest-first
Date: Wed, 14 Mar 2018 11:03:39 +0100
Message-ID: <> (raw)
In-Reply-To: <20180314071304.GA17978@dcvr>

On Wed, Mar 14, 2018 at 8:13 AM, Eric Wong <> wrote:
> Nicolás Ojeda Bär <> wrote:
>> Hello,
> Minor nit about the Subject: this affects the PSGI
> PublicInbox::WWW module, which works best with the bundled
> -httpd, but really can work with any PSGI
> (Perl Server Gateway Interface) server.

Thanks for the clarification.

>> Unless I missed something there does not seem to be a way to sort the
>> message list oldest-to-newest. A little arrow somewhere to invert the
>> order would be nice to have.
> Right; it's always favors newest messages.  We usually find
> newer messages more relevant and also git packs are optimized
> for newer data.
> I'll take your request into consideration, but am currently
> against this:
> I don't want to go down the path of making the WWW interface too
> complex or trying to satisfy everybody with it.  User interface
> is a PERSONAL choice and I want it to remain that way.

I share this point of view. Having said that, _personally_ I still
feel reverse date ordering is an important feature to have in the web

> The most important part of the WWW interface is it has a stable
> URL format for downloading mboxes and Atom feeds.  These allow
> and encourage users to use their favorite tools locally to
> consume them.  Supporting NNTP is another key to encouraging
> users to choose their own UIs.
> To that end, the bundled -httpd and -nntpd servers are designed
> to handle aggressive clients fairly even if they simultaneously
> download huge amounts of messages.
> Thanks for the interest.

Thanks for your work!


  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-11  9:17 Nicolás Ojeda Bär
2018-03-14  7:13 ` Eric Wong
2018-03-14 10:03   ` Nicolás Ojeda Bär [this message]
2019-06-15 20:37     ` 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 \ \ \ \ \

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

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Example config snippet for mirrors

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone