Live data from Hacker News

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

developer.chrome.com

161–170 of 253 posts

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

#161

Earlier quoted context omitted.

> My question was why google reader was good, not why it was popular. Once you learn about Venn diagrams it's going to completely blow your mind. One easy first pass at making inferences as to best services is to use popularity as an imperfect first proxy. So if someone says that a service became a de facto standard used by all of the internet, it's one of the ways to helpfully frame the conversation about whether th…

> Once you learn about Venn diagrams it's going to completely blow your mind. One easy first pass at making inferences as to best services is to use popularity as an imperfect first proxy. So if someone says that a service became a de facto standard used by all of the internet, it's one of the ways to helpfully frame the conversation about whether the service proved to be useful. Of course there will be exceptions, b…

>I completely reject this analysis, as there are numerous counterexamples of things that are popular but not good,

Yikes, did you miss the part where I explicitly acknowledged that there are counterexamples? And since you missed it the first time, I guess I'm going to repeat it again here for emphasis. Yes, there are indeed counterexamples. Broad brush inferences always have counterexamples, and nevertheless are useful indicators. I spent a whole paragraph talking about the functional literacy of understanding why it's a good first approximation. People drive Priuses, people use iPhones, people listen to Taylor Swift. And each of those cases there's a a Venn diagram overlap between popularity and positive user experience where the former can be a proxy for the latter. If you genuinely don't understand how that argument works there's a functional literacy issue here. Moreover, there are counterexamples but this isn't one of them! This specific case, is one of those cases where popularity and positive user experience coincide, which was the whole point to begin with. Being obtuse about how those are connected is just a waste of everybody's time.

>Now that actually answers my question,

Well the crux of this conversation has been that this is an obtuse question in the first place, and that your preferred framing of the question in terms of user experience to the exclusion of popularity was an obtuse refusal to understand the significance of how those things meaningfully overlap, and it was obtuse in the sense of ignoring a broader conversation about mainstream adoption of RSS. The conversation was about that but you wanted to specifically turn it into an end user question.

>which seems like it would have been a recipe for success given the outcry and hunger for Readeer.

Copies of it do exist, often with features paywalled. Part of the downward spiral from de facto standard to boutique experience.

>Even looking at the proportion, it's more than likely still higher today, at least in terms of websites-with-RSS.

However you measure it, it is no longer the de facto standard that it once was. You don't see the RSS icon next to the social media icons on websites. Google News, Twitter, and craigslist removed their RSS functionality, mainstream browsers have removed their built-in RSS functionality, and, again I have to raise the functional literacy thing, because look at what you're saying. The best justifications of RSS are this combination of scaffolding and duct tape about how if you squint and think about it you can still find it, it's just an entirely different universe than it being a de facto standard.

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

#162

RSS requires a lot of developer resources to work with. AdSense, for example, is super hard to fit into RSS. How do you do it? 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.

I think this is satire. This is satire right?

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

#163

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 "Internal issues have been filed with the DevSite team" to get worked on [3]. And who knows when this will rise to a priority for that team? In the old Google, it would have been easier for anyone t…

[deleted]

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

#164
post #148
post #133

Hey all, I lead the team that runs this site. We moved our site to a different infrastructure that doesn't support the automatic generation of RSS feeds. I'm painfully aware that this isn'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. We are working on making sure this lands asap. Paul

> We moved our site to a different infrastructure that doesn't support the automatic generation of RSS feeds. I had been wondering why https://developer.chrome.com/feeds suddenly died. > I needed our team to hit a deadline Why?

Probably related to whatever reason the site was moved in the first place, but regardless an internal Google deadline is unlikely to be met with anything other than "so what, fix RSS first" in this thread.

The majority of corporate deadlines are fictional in the sense that there is not a regulatory or legislative component to them, so it's easy to hand-wave them away and say that $THING should be a higher priority than the deadline. But that doesn't make them any less real for the people who have that deadline imposed by their boss (or more realistically, their boss's boss's boss's boss).

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

#165

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 "Internal issues have been filed with the DevSite team" to get worked on [3]. And who knows when this will rise to a priority for that team? In the old Google, it would have been easier for anyone t…

when roughly would you place the "old Google" turning point?

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

#166

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 o…

And since then, the other browsers have removed their native RSS/Atom feed support. Firefox and Safari both used to have it and have since removed it. Visiting an RSS feed in Safari now shows you a page that resembles a 404, telling you that Safari no longer supports feeds.

> Visiting an RSS feed in Safari now shows you a page that resembles a 404, telling you that Safari no longer supports feeds.

For me it shows an alert asking if I want to subscribe in my installed feed reader.

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

#167
post #154
post #148

Earlier quoted context omitted.

> We moved our site to a different infrastructure that doesn't support the automatic generation of RSS feeds. I had been wondering why https://developer.chrome.com/feeds suddenly died. > I needed our team to hit a deadline Why?

There's lots of reasons some of which I can't go into details about, but there are some that I can: There is a freeze to the new infrastructure's product features until after the new year and we needed to get this in before then (we can land feed support without a product feature change) The people I have working on the older infrastructure will be on new projects for our team in the new year.

Were the deadlines, feature freezes, and project reshuffling imposed on you from above, or were they your decisions?

In a blog post two months ago you said, "I've taken the decision..." https://web.dev/blog/webdev-migration

There was clearly someone in Google management who decided that RSS could be broken.

Why is this important? Well, for example, it seems that the RSS feed was already broken when this important announcement was posted: "Resuming the transition to Manifest V3" https://developer.chrome.com/blog/resuming-the-transition-to...

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

#168

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 o…

There are three additional reasons: * Google Reader is often cited as the best RSS Reader but was killed, which reduced amount of users (I never used it, thus can't judge it) * Many publishers want people to go to their site, thus don't provide full feeds, only headlines and limit it in additional ways. * People went to Twitter and Facebook as their news aggregators, depending on the social graph to preselect "releva…

> Google Reader is often cited as the best RSS Reader but was killed

1. Google Reader was not necessarily the best reader. The anger and frustration with the handling of Google Reader lies in the fact that Google Reader was the first reader from a major tech company. That essentially killed all the other innovation in this space and then Google Reader was itself killed in such a short span that there wasn’t an opportunity to have a smooth transition for the entire industry with it.

2. The one spade that did see a lot of competition growth and innovation were off-web RSS clients (precisely because Google Reader wasn’t a player in this space). But even these were completely handicapped by the elimination of Google Reader because Google Reader has become the de facto syncing solution for your RSS list and read states, etc. Again, the short time between announcement and end of life meant many of the popular clients couldn’t find a smooth transition for their users.

3. Google Reader had a social network effect component where someone could publish RSS articles they were reading and others could subscribe to their feed. In this sense it almost acted as an alternative to Twitter. The Twitter implosion has shown exactly how hard it is for alternatives to a social network to arise (because you invariably get many alternatives and it’s hard to get everyone onto one).

And the RSS reader social network space was nascent so the fragmentation as a result of the destruction of Google Reader meant a lot of people migrated to Twitter instead (Google had hoped they would migrate to Google+ instead but Google+ was awful so that didn’t happen).

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

#169

Earlier quoted context omitted.

> Once you learn about Venn diagrams it's going to completely blow your mind. One easy first pass at making inferences as to best services is to use popularity as an imperfect first proxy. So if someone says that a service became a de facto standard used by all of the internet, it's one of the ways to helpfully frame the conversation about whether the service proved to be useful. Of course there will be exceptions, b…

>I completely reject this analysis, as there are numerous counterexamples of things that are popular but not good, Yikes, did you miss the part where I explicitly acknowledged that there are counterexamples? And since you missed it the first time, I guess I'm going to repeat it again here for emphasis. Yes, there are indeed counterexamples. Broad brush inferences always have counterexamples, and nevertheless are usef…

My dude, you seem very hostile. What is your problem?

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

#170

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 o…

Vivaldi has that built in and a good RSS reader as well. Still very useful.

I use Vivaldi to detect the RSS and grab the URL, but actually have my RSS in Thunderbird. Back in the days of good Opera, I had mail, chat, RSS all inside the browser. But for some reason I couldn't get back to that when Vivaldi finally released the mail beta.

So not saying Vivaldi's RSS is bad, mostly want to mention that Thunderbird can do RSS too, if one happens to use it anyway.

Post reply on HN