Nick Schonning

@anurag629 anonymous commenting doesn't exist in this project https://github.com/giscus/giscus/issues/65

The built-in release feed contains the information except the download links that were only available on the website feed. If @nodejs/releasers wants to modify the process for the release posts...

> I'm strongly leaning towards not implementing this as I'm not sure how worth it is, and so far no one has been complaining about missing "description" for the RSS...

> What built-in release feed? What sort of information was only available on the website feed? Could you please point what is being done differently? The link from the description...

> The release blog posts are too long to include as a `description`, for example. And what I'm debating here is how valuable it is to add a `description` here,...

The GitHub feed was never sourced. It's an automatic feed created/updated when releases are created on the nodejs/node repo. What I meant was that previously, even with the truncation, most...

You're probably on to something with the sourcing/delegating of the GitHub release feed. It would just need buy-in to harmonize the missing content from the template https://github.com/nodejs/nodejs.org/blob/main/scripts/release-post/template.hbs (download links, sha,...

Yup, you've raised some points that may simplify things: - Delegate the Release feeds/pages to the `nodejs/node` releases. That would skip @nodejs/releasers needing to do the PR to this repo,...

I'm now remembering that the GitHub release page does have a character limit that was hit in the past. Not sure if that is still an issue or something that...

You don't say what the problem is, but I tried to look at it because I was currious. I think there are bad uses of `:where`. I tried using prettier...