Hacker News new | past | comments | ask | show | jobs | submit login

1) This makes perfect business sense: Google failed to create its own social feed that would stick, so instead it's piggybacking off of a standard technology (and I'm sure it'll collect plenty of data just like it would from an actual social feed). This is what Google did in the early days with other technologies like the open web and email, and it's generally a good thing for everybody (until they enter the "extend" and "extinguish" phases later on)

2) Question as someone who's new to RSS: is there a standard URL path that a reader can use to automatically find your XML feed? I've already added RSS to my site, but right now there's just a home page link to the XML document, I'm not sure how it would be auto-discovered for such a "follow" button




Generally, you can add a <link> tag in the header, but in practice many websites forgo this or mess up the implementation, so most feed readers have custom search algorithms to try and find them.

Just looked through the Chromium source code, the algorithm for finding RSS feeds is here: https://source.chromium.org/chromium/chromium/src/+/main:com...

[0] https://pypi.org/project/feedsearch/ [1] https://fetchrss.com/api


> Question as someone who's new to RSS: is there a standard URL path that a reader can use to automatically find your XML feed?

Yes. Add a link like this:

<link rel="alternate" type="application/rss+xml" title="My articles" href="/articles/rss/" />

(Or more likely, application/atom+xml -- rss is not great, atom is generally what you want, and what you'll be publishing)


RSS is not great but I abhorred atom with a passion back when I was working with feeds. It was a way overcomplicated xml mess. RSS is so much simpler to work with, you just have to deal with less than stellar documentation.


My impression was the opposite: RSS had so many warts and inconsistencies that you needed complex heuristics & a big test suite to handle things like encodings, relative links, and extensions whereas a single XML parse was all I needed for Atom. The authors had clearly learned the lessons from the early feed producer/consumer projects and tried to avoid making similar problems.


Your impression is correct.


Nice! I'll add that. Probably I'll just add both versions.


Honestly adding both isn't necessary. Just use Atom because RSS is an ill defined hodgepodge.

I work for a service that creates "RSS" feeds as a side effect of what we do and they've all be Atom for 10+ years with no issues.

Please let the RSS format die.


RSS is like FTP.

In theory it's a simple protocol, but there are so many differing implementations that it's a full-time job to keep up with all the little warts.


I have no horse in this race (I don't even know what Atom is tbh; I'm inferring that it's some kind of refined subset and/or extension of the RSS spec), and I'd prefer my site to be accessible to as many readers as possible.


Atom is basically RSS' successor, fixing some ambiguities in RSS' (lack of) spec.


RSS 2 would've been far less confusing


Unfortunately not. “RSS 2.0” is the current version of old rss


Okay, fine; call it RSS 3.0


But do you ever saw newer version that is simpler ? :) With less features or not-backward-compatible or without mechanism for plugging developed in future extensions...

Making complicate protocol simpler require process equivalent to rewrite in software. Re-architecture the basics. It is more then seldom to the point you can think all that complications are intentional.

One example of simplification that happen in IT is UTF-8. But it was more a replacement and big companies didn't switch anyway...


There is no standard URL but there is a standard link from the website to the feed: the <link> element in the header. See https://www.rssboard.org/rss-autodiscovery




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: