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

171–180 of 253 posts

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

#171

Post by Devasta »

hliyan wrote: 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…

User experience has long been superseded by developer experience. You can see it in how both camps operate, dev tools are snappy command line apps but end users get electron slop.

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

#172

Post by Ajedi32 »

pc86 wrote: post #164
lapcat wrote: 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?

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

"so what, fix RSS first" seems like a valid criticism even if it really is true that this isn't something this particular person has any control over. If your organizational structure is forcing you to do something dumb, then there's a problem with your organizational structure.

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

#173

Post by dagurp »

kinlan wrote: post #154
lapcat wrote: 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.

There was a bug in the old RSS implementation (the last-updated date was always Jan 1st 1980) so it would be great if you fixed that when you re-add it

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

#174

Post by tehlike »

culi wrote: post #165
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…

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

Arrival of Sundar as CEO was the obvious sign, but probably few years before then.

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

#175

Post by listmaking »

culi wrote: post #165
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…

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

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 first place is what Google did wrong.)

This is actually ironic in light of popular HN sentiment in Google-related articles, where many seem to imagine Google acting as a single whole, rather than different teams working in their own interests and not thinking of the big picture. E.g. people in this thread imagining that "Google" thought about RSS support and made a decision based on advertising revenue (or whatever imaginative reason), when in fact the team working on the "DevSite" infrastructure probably barely thought about RSS at all. Maybe they should have, but the reality that RSS (unfortunately) doesn't matter much seems harder to swallow for many, than theories about maliciously breaking it.

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

#176

Post by ascagnel_ »

latexr wrote: post #166
TazeTSchnitzel wrote: post #141

Earlier quoted context omitted.

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.

And if you don't have a feed reader installed, that modal will send you to the App Store, with "RSS" as the search term (at least on macOS).

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

#177

Post by thowawatp302 »

glenstein wrote: post #114
marginalia_nu wrote: post #58

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…

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

[dead]

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

#178

Post by sertbdfgbnfgsd »

bArray wrote: post #9
sertbdfgbnfgsd wrote: post #6

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

> Google has an interest in our depending on Google to find stuff, so of course they see RSS as a threat. But they historically had several feed systems [1] [2] which were fully under their control. > Cue some "googler" show up defending this move and how it makes the world better. Of course. 'We have a better system that uses 2FA to securely text you every ten minutes to generate a code that, in combination with a 1…

> But they historically had several feed systems [1] [2] which were fully under their control.

I don't think Google's fear is who's in control of any one particular RSS. I think Google's fear is what if people realize that, for the purposes of subscribing to updates from a source, RSS is objectively better than Google. They're afraid of losing the mindshare of being the unquestionably better option for everything.

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

#180

Post by tehlike »

listmaking wrote: post #175
culi wrote: post #165

Earlier quoted context omitted.

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

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

Post reply on HN