We don't have official RSS feed support for now, but we're working on a solution

This is hilarious big-company shit, that engineer on Chrome devrel team finds it easier to actually just write his own unofficial RSS feed-generator and make it public [1] — the feed for this blog is at [2] — than for the &quot;Internal issues have been filed with the DevSite team&quot; to get worked on [3]. And who knows when this will rise to a priority for that team?<p>In the old Google, it would have been easier for anyone to just fix this internally.<p>(Disclaimer: work at Google but not on anything related to this; all my information comes from links in this HN thread. Which is ironic &#x2F; symptom of the same problem.)<p>[1]: <a href="https:&#x2F;&#x2F;front-end.social&#x2F;@bramus&#x2F;111448166340277056" rel="nofollow noreferrer">https:&#x2F;&#x2F;front-end.social&#x2F;@bramus&#x2F;111448166340277056</a> and <a href="https:&#x2F;&#x2F;github.com&#x2F;bramus&#x2F;web-dev-rss">https:&#x2F;&#x2F;github.com&#x2F;bramus&#x2F;web-dev-rss</a> &#x2F; <a href="https:&#x2F;&#x2F;github.com&#x2F;bramus&#x2F;chrome-for-developers-rss">https:&#x2F;&#x2F;github.com&#x2F;bramus&#x2F;chrome-for-developers-rss</a><p>[2]: <a href="https:&#x2F;&#x2F;chrome-for-developers-rss.bramus.workers.dev&#x2F;blog" rel="nofollow noreferrer">https:&#x2F;&#x2F;chrome-for-developers-rss.bramus.workers.dev&#x2F;blog</a><p>[3]: <a href="https:&#x2F;&#x2F;issuetracker.google.com&#x2F;issues&#x2F;314910854#comment2" rel="nofollow noreferrer">https:&#x2F;&#x2F;issuetracker.google.com&#x2F;issues&#x2F;314910854#comment2</a>

Hey all, I lead the team that runs this site.<p>We moved our site to a different infrastructure that doesn&#x27;t support the automatic generation of RSS feeds.<p>I&#x27;m painfully aware that this isn&#x27;t the best solution right now. I needed our team to hit a deadline for migrating all the content to the new system, and then manage cleanup of known missing functionality after.<p>We are working on making sure this lands asap.<p>Paul

When chrome started taking over, all other major browsers (probably even internet explorer) had native RSS read support (read at least). They use to show rss icon in the url bar or some other indictor that this site has RSS available. But Chrome ever since has been throwing raw xml at you when you try to open an rss feed link and never indicates if there is RSS here. I believe this to be the main reason for decline of RSS.

The web seems to be becoming paradoxically less and less machine&#x2F;automation friendly. I recently had to modify 150+ accounts in a Google Workspace. Twenty years ago, I would be doing this in a Unix environment with a very simple shell script. Instead, I had to click-copy-paste-click, 20 times per page, like a monkey. I&#x27;m sure there must be some sort of API, but it would have taken 100 times the time it would have taken to write a simple command line script. In the quest for more and more human eyeballs, the web is becoming less and less machine friendly.

I feel pleased that me as a single web dev with minimal money and few smarts, has managed to successfully implement rss on all blogs or blog like things I&#x27;ve made.<p>Perhaps I should interview at Google and teach them my amazing solution.

&gt; If you&#x27;ve ended up here, chances are you&#x27;re looking to subscribe to our blog in your RSS feed.<p>&gt; Unfortunately, we don&#x27;t have official RSS feed support for now, but we&#x27;re actively working on a solution.<p>Well, that certainly means they are going to have RSS feeds in the future. Right?

&gt; Unfortunately, we don&#x27;t have official RSS feed support for now, but we&#x27;re actively working on a solution.<p>RSS could be that solution!

I noticed the same for Google&#x27;s site <a href="https:&#x2F;&#x2F;web.dev&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;web.dev&#x2F;</a><p>The last article pushed to the feed was &quot;Changes to the web.dev infrastructure&quot; few months ago <a href="https:&#x2F;&#x2F;web.dev&#x2F;blog&#x2F;webdev-migration" rel="nofollow noreferrer">https:&#x2F;&#x2F;web.dev&#x2F;blog&#x2F;webdev-migration</a><p>The feed still there but with no updates <a href="https:&#x2F;&#x2F;web.dev&#x2F;feed.xml" rel="nofollow noreferrer">https:&#x2F;&#x2F;web.dev&#x2F;feed.xml</a> and on the site you can see new articles published.<p>Is sad that on a infrastructure revamp of a modern site, the RSS feed was left out of the features list (at least for now).

Bramus, a google engineer did an inoffical workaround:<p><a href="https:&#x2F;&#x2F;mastodon.social&#x2F;@bramus@front-end.social&#x2F;111448166953123004" rel="nofollow noreferrer">https:&#x2F;&#x2F;mastodon.social&#x2F;@bramus@front-end.social&#x2F;11144816695...</a>

People don&#x27;t understand how much RSS is useful...<p>I&#x27;m still angry at Google for killing Reader. It was the best way to consume content on the web.

Solution found.<p><pre><code> curl -sA &quot;&quot; https:&#x2F;&#x2F;developer.chrome.com&#x2F;blog&#x2F;sitemap.xml \ |sed -n &#x27; 1i\ &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; ?&gt;\ &lt;rss version=&quot;2.0&quot;&gt;\ &lt;channel&gt; s}\(&lt;loc&gt;\)\(.*\)\(&lt;&#x2F;loc&gt;\)}\ &lt;item&gt;\ &lt;title&gt;\2&lt;&#x2F;title&gt;\ &lt;description&gt;\2&lt;&#x2F;description&gt;\ &lt;link&gt;\2&lt;&#x2F;link&gt;\ &lt;&#x2F;item&gt;}p; $a\ &lt;&#x2F;channel&gt;\ &lt;&#x2F;rss&gt; &#x27; </code></pre> If this isn&#x27;t correct RSS, please forgive me. I&#x27;m not an &quot;engineer&quot;. I prefer a personalised, simple HTML made from URLs as opposed to XML. I write filters to generate this in C.<p>NB. The public sitemap.xml still refers to an (unofficial?) RSS feed.

“Unfortunately” - c’mon it wasn’t an act of God that removed them

Related RSS talk today:<p><i>Please, Expose Your RSS</i><p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=38595855">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=38595855</a>

&quot;Removed&quot; implies it was there at some point; is this true? Or has this blog just never had RSS support? (I searched for this blog in Feedly and it didn&#x27;t show up any older feed, but that may not be a reliable method for checking?)

They are “actively working on a solution”, because it requires a Google-sized brain and 28477382 work hours to maintain an RSS feed of a blog. What a silly company.

Broadly, the entire tech community should be embarrassed about the extent to which they actually collectively &quot;believed&quot; Google&#x27;s stated purpose for killing Google Reader; if we had effectively called out that utter BS a while ago, I genuinely believe the entire web would be a better place today.

Why don&#x27;t we use Edge, Firefox, Brave, Opera and so on?

I tried using RSS Generators like <a href="https:&#x2F;&#x2F;createfeed.fivefilters.org&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;createfeed.fivefilters.org&#x2F;</a> and even a graphical one, but it looks like this isn&#x27;t a static site but there&#x27;s some sort of delayed fetch of the posts that messes them up. Regardless how much I tried, I could only get it to fetch the top nav bar. I don&#x27;t really think first of intentional malice to spite everyone else too, but maybe this is the same reason their own RSS feed generator no longer works either.<p>Also, I note the wording of the error message, that they&#x27;re actively working on it.

I have the feeling they&#x27;re currently in the final stages of development for an alternative and want to remove RSS from all their stuff right now to preemptively avoid people lamenting its sudden removal then.

Found this HN post via RSS...

It&#x27;s worth noting that this new site replaces one that was just 3 years old, released in December 2020, here&#x27;s the announcement of that version of the site: <a href="https:&#x2F;&#x2F;developer.chrome.com&#x2F;blog&#x2F;welcome" rel="nofollow noreferrer">https:&#x2F;&#x2F;developer.chrome.com&#x2F;blog&#x2F;welcome</a><p>Loss of the ability to contribute via GitHub pull request is unfortunate, hopefully there will be a better way to contribute again in the future.

Cue...<p>- commercial AI refusing to generate RSS XMLs from a webpages&#x27; content. - &quot;illegal&quot; AI that is willing to browse webpages without disclosing that their&#x27;e bots

I think this site, is not well scrap-able without selenium. Google products however rely on web scraping because of Google search. It is a hypocrisy of sorts.

Let me guess... so users are forced to load a web page which will show them ads that couldn&#x27;t fit into RSS records?

Google, you helped kill widespread RSS adoption to begin with. You can&#x27;t be trusted with anything technology.

&#x27;Google has stopped...&#x27;, or &#x27;Google no longer...&#x27;, &#x27;Google have removed&#x27;.<p>As I can no longer watch yt without getting annoyed, looks like it&#x27;s time to get a new email provider (as well) .<p>@ yahoo seem to have few(er?) problems.<p>There are probably others. Can anyone recommend a good search engine?

Not sure if it counts as dev blog but <a href="https:&#x2F;&#x2F;chromereleases.googleblog.com&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;chromereleases.googleblog.com&#x2F;</a> still has RSS and Atom feeds, I guess not everything got nuked.

<a href="https:&#x2F;&#x2F;kill-the-newsletter.com" rel="nofollow noreferrer">https:&#x2F;&#x2F;kill-the-newsletter.com</a><p>please donate: <a href="https:&#x2F;&#x2F;patreon.com&#x2F;leafac" rel="nofollow noreferrer">https:&#x2F;&#x2F;patreon.com&#x2F;leafac</a>

To be fair, HN doesn&#x27;t offer RSS either. We need it!

I think this thread could good place to share services (self-hosted or paid) that allow to monitor site for changes and make rss&#x2F;send notification.

Google&#x27;s fight against open technologies continues.

RSS is not aligned with Google&#x27;s business goals.

Guess they don’t want people to read their pages.

It makes sense. After killing Google Reader making RSS less relevant helps to justify that as the right decision :)

Google is a joke how does something like this even happen<p>Sometimes I think the jokes about Google having no management are true.

Watch them slowly remove every RSS feed they operate, so when they come up with their own proprietary solution in 6 months nobody can lament their &quot;sudden&quot; removal of RSS.

*-in-cheek-on<p>Google management too busy doing evil

There&#x27;s a ton of smart people working at Google. Just none in the management

Maybe they can find the code for reader somewhere on a backup disk?

The real crime is using Google tools&#x2F;libraries

Wasn&#x27;t Google planing to add some sort of RSS support in Chrome? Or did the experiment end as a failure?

which rss reader do you use?

Bard solvable?

what year is it

Google has an interest in our depending on Google to find stuff, so of course they see RSS as a threat.<p>Cue some &quot;googler&quot; show up defending this move and how it makes the world better.

It&#x27;s too much work and effort to maintain such complicated legacy technology for the incredibly busy brain of a Google engineer.

RSS reader software won&#x27;t be successful. RSS reader should be built into the browser and every time you open the browser, the RSS feed should be the landing page. Every time you open a new tab, it should show a minimal feed that can be fully expanded.

If keeping up with Google dev blogs is important to you, at Monitoro[0] we support alerts even if the website doesn&#x27;t offer RSS. You can also catch specific updates, for example if a new post mentions a Google tool you&#x27;re using at work.<p>Feel free to get in touch with me if you need help or have questions.<p>[0]: <a href="https:&#x2F;&#x2F;monitoro.co" rel="nofollow noreferrer">https:&#x2F;&#x2F;monitoro.co</a>

RSS requires a lot of developer resources to work with.<p>AdSense, for example, is super hard to fit into RSS. How do you do it?<p>Sorry, we tried everything but the user agent support for Javascript in RSS is simply lacking. Unfortunately, it has to be dropped, there is no alternative.