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

101–110 of 253 posts

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

#101
post #29

> Unfortunately, we don't have official RSS feed support for now, but we're actively working on a solution. RSS could be that solution!

I was wondering about that wording as well, it's such a weird way to word it. You had a feature, you took it way, and now you're working on a solution... for what?

Did Google develop a new internal blogging platform and just didn't get around to supporting RSS?

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

#102
post #47

Earlier quoted context omitted.

You run a search engine and don't understand why defaults matter? Google pays billions to be the default. I don't understand what you don't understand. RSS was the default. Then it "died" (became non-default) and we got the Facebook feed and Twitter's toxic impression-pumping algorithms, and it's so much worse. Journalists depended on Reader the way they came to depend on Twitter. They didn't move to another reader.

RSS feeds are still very much around regardless of Google's actions. I'm looking at it from a user's perspective, not the operator's perspective, at what service is being offered? My question was why google reader was good, not why it was popular. As for my search engine, I genuinely don't track my users, so I really don't have the fainest how many users I have. 4 people or a million people use my search engine, and…

RSS feeds are still around, but they're starting to disappear. Like, eg, Google removing RSS support from their developer blogs...

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

#103

Not sure if it counts as dev blog but https://chromereleases.googleblog.com/ still has RSS and Atom feeds, I guess not everything got nuked.

googleblog.com runs on Blogger so has full RSS support. Presumably these other blogs were using something "custom" and after some rewrite/overhaul RSS support didn't hit the priority line.

In a cohesive organization they would improve Blogger to fulfill their needs, but instead they just waste resources recreating a one-off solution over and over again.

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

#104

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

“We are actively working on a solution…”

Good job they specified "actively", or we might've thought they were working on it some other way.

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

#105
post #30
post #2

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

No no no, they're working on "a solution". That means they will built Google Updates™, a locked-down walled-garden push system with premium tiers.

Which they will a year later kill because it didn't become the new AdSense.

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

#106
post #69

The web seems to be becoming paradoxically less and less machine/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'm sure there must be some sort of API, but it would have taken 100 times the time it would have tak…

> I'm sure there must be some sort of API

There is, but somehow, rather than being a workspace API, it's a GCP api ; and so if you want to use it, there is a big step to climb.

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

#107
post #75

Earlier quoted context omitted.

I would guess that rss doesn’t show up in their JavaScript-driven web analytics so they mistakenly think no one uses it. So they have some stupid conversation like “patching the rss code will take 5 units of labor, but I want to cyberdize the whoozit that also takes 5 units. Does anyone even care about rss and use it? Oh the analytics show zero. Let’s de prioritize that.” I think the bigger problem is people on the t…

>they mistakenly think no one uses it. No, I think it's a very deliberate choice. RSS is a means to escape the gaze of Big G. Can't let that happen

I have to imagine that for a chrome releases and developer updates blog that this has absolutely nothing to do with ensuring someone uses search or ads and more just plain priorities and no one bothering to add RSS after they upgraded the site. Occam's razor and all that

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

#108

Earlier quoted context omitted.

RSS feeds are still very much around regardless of Google's actions. I'm looking at it from a user's perspective, not the operator's perspective, at what service is being offered? My question was why google reader was good, not why it was popular. As for my search engine, I genuinely don't track my users, so I really don't have the fainest how many users I have. 4 people or a million people use my search engine, and…

RSS feeds are still around, but they're starting to disappear. Like, eg, Google removing RSS support from their developer blogs...

I'd say more websites have RSS or Atom feeds than not, based on looking at the data coming out of my crawler. Google's devblogs just aren't really particularly important.

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

#109
post #75

Earlier quoted context omitted.

I would guess that rss doesn’t show up in their JavaScript-driven web analytics so they mistakenly think no one uses it. So they have some stupid conversation like “patching the rss code will take 5 units of labor, but I want to cyberdize the whoozit that also takes 5 units. Does anyone even care about rss and use it? Oh the analytics show zero. Let’s de prioritize that.” I think the bigger problem is people on the t…

>they mistakenly think no one uses it. No, I think it's a very deliberate choice. RSS is a means to escape the gaze of Big G. Can't let that happen

I think you're falling prey to Hanlon's Razor. What probably happened here is something approaching the following conversation:

$PM: Hey $ENGINEER, it looks like this "arr ess ess" thingy has very few users, do you know what it does?

$ENGINEER: Yeah, it's a web standard that publishes a feed of updates to our website. It's kind of neat actually, if you have an RSS read--

$PM (waving hands): okay skip the wikipedia article, that's fine; but does it generate revenue?

$ENGINEER (blinking): uh...no, it doesn't. Anyone can query our RSS feed and update their local cache of articles and read them later, it's actually really useful if you're ever somewhere without interne--

$PM: So we can't monetize this?

$ENGINEER: ...no, this is an RSS feed for a tech blog. We can't monetize this.

$PM: If you remove this and integrate $FEATURE on $PAID_SERVICE, I'll write you a better peer review this year. It's reducing tech debt right? This sounds like an old school thing anyway, I've never even heard of it!

$ENGINEER (heavy sigh): Yeah, whatever man.

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

#110
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.

Post reply on HN