unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: [PATCH] view: remove mbox.gz and Atom from topic view
Date: Mon, 16 Aug 2021 23:35:20 +0000	[thread overview]
Message-ID: <20210816233520.GA1729@dcvr> (raw)
In-Reply-To: <20210816154444.sj3ks2sikq3x2ywx@nitro.local>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> - I don't think most people would choose to download mbox.gz or click on the
>   "Atom" link from the thread listing page -- there is a thread view for this
>   purpose.

Agreed, I don't think I've ever used them from the topic page...

Fwiw, I use mbox.gz downloads from per-topic pages, but I'm not
sure I've ever used Atom feeds outside of testing.

> - Removing this would save quite a few bytes from being transferred
>   unnecessarily and speed up page rendering.

Probably, the Message-ID being repeated ought to be good for
compressibility, but not having it at all would be more
efficient.

------8<-----
Subject: [PATCH] view: remove mbox.gz and Atom from topic view

This declutters the topic view since these links seem rarely
used.  Atom and mbox.gz links probably make most sense when
users have read the HTML and decide the topic is worth following
or downloading.

Reported-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Link: https://public-inbox.org/meta/20210816154444.sj3ks2sikq3x2ywx@nitro.local/
---
 lib/PublicInbox/View.pm | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/lib/PublicInbox/View.pm b/lib/PublicInbox/View.pm
index c80a675e..17d38302 100644
--- a/lib/PublicInbox/View.pm
+++ b/lib/PublicInbox/View.pm
@@ -1154,10 +1154,8 @@ sub dump_topics {
 			$anchor = '#t'; # thread skeleton
 		}
 
-		my $mbox = qq(<a\nhref="$href/t.mbox.gz">mbox.gz</a>);
-		my $atom = qq(<a\nhref="$href/t.atom">Atom</a>);
 		my $s = "<a\nhref=\"$href/T/$anchor\">$top_subj</a>\n" .
-			" $ds UTC $n - $mbox / $atom\n";
+			" $ds UTC $n\n";
 		for (my $i = 0; $i < scalar(@extra); $i += 2) {
 			my $level = $extra[$i];
 			my $subj = $extra[$i + 1]; # already normalized

  reply	other threads:[~2021-08-16 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 15:44 RFE: remove "- mbox.gz / Atom" from thread listing Konstantin Ryabitsev
2021-08-16 23:35 ` Eric Wong [this message]
2021-08-17  0:26   ` [SQUASH] fix tests for missing t.mbox.gz links Eric Wong
2021-08-17 14:07   ` [PATCH] view: remove mbox.gz and Atom from topic view Konstantin Ryabitsev

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=20210816233520.GA1729@dcvr \
    --to=e@80x24.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=meta@public-inbox.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).