From: Eric Wong <firstname.lastname@example.org> To: "Nicolás Ojeda Bär" <email@example.com> Cc: firstname.lastname@example.org Subject: Re: public-inbox-httpd feature request: sort oldest-first Date: Sat, 15 Jun 2019 20:37:19 +0000 [thread overview] Message-ID: <20190615203719.5un64ihnkf7b74gf@dcvr> (raw) In-Reply-To: <CAPunWhD85aNDEg1Uk_fc1-a9zP+_C431y0YHD0MUHq4JVvV22w@mail.gmail.com> Nicolás Ojeda Bär <email@example.com> wrote: > On Wed, Mar 14, 2018 at 8:13 AM, Eric Wong <firstname.lastname@example.org> wrote: > > Nicolás Ojeda Bär <email@example.com> wrote: > >> 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: So I've realized reversing results can be faster than "git blame" in some cases, so I've implemented this: https://firstname.lastname@example.org/T/ > > 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. So I didn't state this before; but one of my concerns was about extra parameters and inconsistent ordering leading to duplicate cache entries (in either the client or varnish). So I managed to overload the "o=" paramter to use negative values, which makes sense to users of Perl (and similar) languages which allow negative array indices to look backwards. I'm actually regretting making "x=" a separate parameter, instead of just replacing "q="... So I might also start 301-ing search requests to enforce a consistent ordering for cache-friendliness... > 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 > interface. Fair enough. I'm considering developing some sort of REST API or just for search; since their's no provision for it in NNTP; and IMAP search capabilities are too limited.
prev parent reply other threads:[~2019-06-15 20:37 UTC|newest] 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 2019-06-15 20:37 ` 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: 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=20190615203719.5un64ihnkf7b74gf@dcvr \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: public-inbox-httpd feature request: sort oldest-first' \ /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
Code repositories for project(s) associated with this 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).