Hacker News Board Hacker News, browsed like a classic message board
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

Post reply on HN
Print view View original

211–220 of 253 posts

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

#211

Post by iamgopal »

kinlan wrote: 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

Can you elaborate on why it’s difficult to add ? I mean it is not looking like technological problem,

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

#212

Post by brandensilva »

tehlike wrote: post #180
listmaking wrote: post #175

Earlier quoted context omitted.

Well it's all gradual and diffuse; for that matter there are still pockets of the "old Google" around today. My point here was just about, in a big company, different teams having their own domains that you don't/can't interfere in, rather than a free-for-all where everyone feels part of the same whole and can just jump in. (Which was probably never going to work anyway, so maybe encouraging such a culture in the fir…

Agree with this take. People always assume some ulterior motive to every single decision google does, but things are often much simpler than that, and mostly all it comes to prioritization...

I hear ya but who sets the priorities? Management typically right? So if they don't see value in RSS and move their KPIs it will never be implemented.

And well profit motives push managements decisions so it's no wonder it never got prioritized. Nothing nefarious about it. RSS makes Google no money.

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

#213

Post by JohnTHaller »

listmaking wrote: post #153

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…

Not sure how old 'old Google' was. There was a bug in the Contacts web app where the states were out of order. They were ordered by 2 digit state ID but shown as state name. A simple order by mixup in SQL. This meant users in New York couldn't tab to the state and start typing the state name to get the state. It was a filed bug. Known by people within Google who wanted it fixed. It was finally fixed this year after nearly a decade.

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

#214

Post by tehlike »

brandensilva wrote: post #212
tehlike wrote: post #180

Earlier quoted context omitted.

Agree with this take. People always assume some ulterior motive to every single decision google does, but things are often much simpler than that, and mostly all it comes to prioritization...

I hear ya but who sets the priorities? Management typically right? So if they don't see value in RSS and move their KPIs it will never be implemented. And well profit motives push managements decisions so it's no wonder it never got prioritized. Nothing nefarious about it. RSS makes Google no money.

At the team level? Eng lead, pm lead, someone who cares about a problem.

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

#215

Post by lapcat »

kinlan wrote: post #208
lapcat wrote: post #167

Earlier quoted context omitted.

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

> Were the deadlines, feature freezes, and project reshuffling imposed on you from above, or were they your decisions? They were my decisions based on all the data I had, including launching with what we had. re: "Resuming the transition to Manifest V3" this was posted on the old infrastructure and should have been in your RSS feeds up until late last week when our migration happened - so for just under a month... I…

According to my backups, https://developer.chrome.com/feeds had XML with 2023-10-17T00:00:00Z until December 7, then HTML after December 8. So it wasn't entirely broken until December 8 but seems to have been frozen for some time before that.

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

#217

Post by prepend »

passwordoops wrote: post #91
prepend wrote: 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

Or maybe they gaslight that as the reason. Their blog post talks about how they don’t have resources and they are prioritizing.

So I agree the real reason is that google doesnt want people using minimally tracked file downloads and thinks they can shovel people towards their more data rich analytics and content consumption.

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

#218

Post by prepend »

rollcat wrote: post #159
prepend wrote: 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…

> I would guess that rss doesn’t show up in their JavaScript-driven web analytics so they mistakenly think no one uses it. All it would take is ?utm_source=rss, but betcha readers would start stripping that, because once you've started abusing everything , anything will look like abuse.

I always include that stuff unless it breaks my experience.

Both to respect the publishers preferences and it’s easier to cut and paste rather than edit the clipboard.

Post reply on HN