Claudio Wunder

> The link from the description [nodejs/node/releases.atom](https://github.com/nodejs/node/releases.atom) I have genuinely never seen this file before. Could I get some context on what this `releases.atom` file is used for, and who...

> The feeds previously did include everything (most of the time), and that made the posts readable and actionable (Eg: downloading a release from the links directly from an RSS...

> 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,...

> The old feed had 20 entries, e.g. [web.archive.org/web/20230103023604/https://nodejs.org/en/feed/releases.xml](https://web.archive.org/web/20230103023604/https://nodejs.org/en/feed/releases.xml) from the beginning of the year. That is fair. Apparently, the `metalsmith-feed` plugin has a default limit of `20` entries. As...

> I'm not sure i'd bet on AMP. Since Google removed the search incentive, I believe larger platforms have been dropping support, so I don't think it's future looks healthy...

Anyhow, let's sulk this in for a while, and get some more opinions from @nodejs/releasers and @nodejs/website folks and see if we find an agreement, something that we feel like...

> I see from a quick scan, a few [instruction posts](https://dev.to/j471n/how-to-add-rss-feed-in-nextjs-blog-34j1) mention a post.exerpt, so maybe there is a built-in piece that might handle the old truncation. That might be...

I wouldn't consider this an issue. Since this only happens with very specific sizing/resizes that usually need to be more natural. We've tested on numerous viewports for mobile devices, tablets,...

> True indeed! I'd just thought I'd mention it though, not sure where exactly this is set but it seems like a relatively easy fix? It might be, haven't investigated...

Any updates here?