From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [RFC v2] www: add topics_(new|active).(html|atom) endpoints
Date: Fri, 10 Nov 2023 12:16:49 -0500 [thread overview]
Message-ID: <20231110-colorful-nippy-octopus-9b1e6a@nitro> (raw)
In-Reply-To: <20231110030959.M879021@dcvr>
On Fri, Nov 10, 2023 at 03:09:59AM +0000, Eric Wong wrote:
> > Yes, actually thinking about this some more, perhaps it makes sense to expose
> > this as an RSS feed feature (maybe even exclusively as an RSS feed feature?).
>
> I assume Atom is OK? I don't know of any widely-used feed readers
> which only do RSS without Atom support. IIRC Atom is less ambiguous
> and supports the in-reply-to extension.
Yes, sorry, I know they aren't the same thing, but in my head Atom is just a
form of RSS (perhaps for the same reason why everyone says "rss reader" but
nobody says "atom reader").
> That said, the Atom feeds generated by this RFC includes full
> messages because that's the easiest way to tie into our existing
> Atom generation code, so it's currently slower than the HTML
> version which never retrieves git blobs.
That's fine, actually, because this lets people read the full message to
figure out if they are interested in the rest of the thread or not.
> > Have two different feeds:
> >
> > - new topics: just all the new threads
> > - hot topics: NN most active threads (kinda lkml.org's "hottest messages")
>
> I'm not sure if `hot' means it's the most read (not just replied-to);
> but tracking read counts isn't something that scales on decentralized
> systems. So I'm naming it "active" instead...
Sounds good to me.
> > Have this available per-list and for the extindex -- I think this would be
> > a great feature that we can point people at as a mechanism to keep an eye on
> > overall activity.
>
> Yeah, lots of the WWW and lei code works transparently between extindex
> and regular inboxes:
>
> extindex:
> https://yhbt.net/lore/all/topics_new.atom
> https://yhbt.net/lore/all/topics_active.atom
> https://yhbt.net/lore/all/topics_new.html
> https://yhbt.net/lore/all/topics_active.html
>
> v2:
> https://yhbt.net/lore/lkml/topics_new.atom
> https://yhbt.net/lore/lkml/topics_active.atom
> https://yhbt.net/lore/lkml/topics_new.html
> https://yhbt.net/lore/lkml/topics_active.html
>
> v1:
> https://public-inbox.org/git/topics_new.atom
> https://public-inbox.org/git/topics_active.atom
> https://public-inbox.org/git/topics_new.html
> https://public-inbox.org/git/topics_active.html
This is great, thank you!
-K
next prev parent reply other threads:[~2023-11-10 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 18:07 Query to see all new "topics" Konstantin Ryabitsev
2023-11-09 2:45 ` [RFC] www: add topics.html endpoint [was: Query to see all new "topics"] Eric Wong
2023-11-09 18:10 ` Konstantin Ryabitsev
2023-11-10 3:09 ` [RFC v2] www: add topics_(new|active).(html|atom) endpoints Eric Wong
2023-11-10 17:16 ` Konstantin Ryabitsev [this message]
2023-11-10 22:23 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://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=20231110-colorful-nippy-octopus-9b1e6a@nitro \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.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.
Code repositories for project(s) associated with this public 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).