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

131–140 of 253 posts

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

#131

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…

> 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, but it's one of those functional literacy things where everyone can understand the significance of why people would bring that up in the context of a conversation that ultimately was closing in on making assessments about the value of the user experience.

I completely reject this analysis, as there are numerous counterexamples of things that are popular but not good, or good but not popular. One does not inform the other, especially in this case where it appears to have derived much of its popularity from Google shoving it onto users by featuring it in their other services.

> Google's RSS reader was simple, ad free, fast, had an elegant design, didn't attempt to push superfluous services or subscriptions, set a standard for accessible anywhere at a time when many popular RSS readers were used on the desktop, and, in contrast to most of the best services now around, was free. I would go so far as to say it was almost unimproveable because it had one job and it did it correctly and didn't try to do other things, which used to be one of the things Google did best.

Now that actually answers my question, but not the question of why someone couldn't just copy this design and carry on when Reader was shut down, which seems like it would have been a recipe for success given the outcry and hunger for Readeer.

> And I feel like none of this information is new, hard to discover, controversial, but is instead part of the generally accepted canon of internet history. So it's a bizarre question to me, if I'm being honest.

Well as I stated in the original question, I never used reader.

> Edit: regarding the prevalence of RSS adoption in the present day, it may be true that as a numeric total there are more sites using it, but that as a percentage it is down. The same way that a winning candidate for president from the 1940s will have fewer votes then a losing candidate from the present day. Numbers will grow over time just due to population growth. Or in the case of the internet, The growth in the number of sites. But to understand whether RSS enjoys the same status as a de facto standard it's necessary to look at more than just the numbers, but at the proportion of adoption today compared to the proportion as an existed in the past.

Even looking at the proportion, it's more than likely still higher today, at least in terms of websites-with-RSS. The websites that tend to not have RSS are very large silo-like websites with enough gravity well to retain users regardless, but these website are by definition few in number and will not affect the statistics in any way.

In the past, it was more common with hand rolled HTML websites, that did not have RSS. These have almost all been supplanted by CMS:es and blog platforms that universally do support RSS.

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

#132
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?

It seems so if I read this right:

https://mastodon.social/@bramus@front-end.social/11144816695...

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

#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

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

#134
post #89

Earlier quoted context omitted.

“We are actively working on a solution…”

it takes passively less than 30 mins to make a RSS feed generator...

Not if you do things the Google way. What takes you 30 minutes takes them 30 weeks.

Google has two big strengths: (1) they build systems at huge scale and (2) they are wildly profitably.

(2) is also weakness because it means they can afford to have highly inefficient processes. It is the reason why Google keeps pushing trash software on the world like Kubernetes (takes that 30 minute project and multiples it by a lot all by itself) as well as cargo cult management processes like OKRs. (Ever see what happens to a startup that is just treading water when management stops everything and introduces a layer of meaningless paperwork?)

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

#135
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

Nice touch in the HN bio!

> RSS is alive https://paul.kinlan.me/index.xml

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

#137

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.

10-20 years later in a court case, these emails will show up.

Exactly, thank you my friend. I'm happy to see that such ideas are entering the mainstream.

(Ok, you and I are probably not the most "mainstream" people in the world, but what I mean is these ideas aren't understood exclusively by antitrust lawyers anymore)

Companies are catching up too though. Google coaches its employees on what language to use internally.

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

#138

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…

RSS is the antithesis to the interest of link aggregators like Google. It is no accident they didn't support it properly.

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

#139
post #10

People don't understand how much RSS is useful... I'm still angry at Google for killing Reader. It was the best way to consume content on the web.

That's probably why they killed it—it gave the end user too much control over content they consume and how they consume it. And of course you can't tell what they actually read or when....

Isn't it possible to simply check when the request to the RSS feed is made? It won't tell you which posts the user read, or even if the user read them at the time of the request (I'm thinking caches), but it could at least tie IP or some other drive-by info to a rough idea of readership.

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

#140

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.
Post reply on HN