ATOM feeds

ATOM feeds

[jidanni]

Reading
http://ehp03.niehs.nih.gov/static/rssFeeds.action
http://ehp03.niehs.nih.gov/static/rssInfo.action
one expects
http://ehp03.niehs.nih.gov/article/feed
to be RSS, but it is ATOM. I suppose the only way to read Atom in gnus
is still via uncomfortable methods mentioned in
http://www.google.com/search?q=gnus+atom .

Re: ATOM feeds

[Ted Zlatanov]

On Tue, 15 Dec 2009 11:40:43 +0800 jidanni@jidanni.org wrote: 

j> Reading
j> http://ehp03.niehs.nih.gov/static/rssFeeds.action
j> http://ehp03.niehs.nih.gov/static/rssInfo.action
j> one expects
j> http://ehp03.niehs.nih.gov/article/feed
j> to be RSS, but it is ATOM. I suppose the only way to read Atom in gnus
j> is still via uncomfortable methods mentioned in
j> http://www.google.com/search?q=gnus+atom .

On my TODO list is integration with Google Reader and other aggregators.
I think nnrss is not as useful as an aggregator for most cases, and
maintaining it in the face of the many broken ATOM and RSS
implementations is a challenge.

Ted

Re: ATOM feeds

[jidanni]

http://www.mediawiki.org/wiki/Special:Code/MediaWiki/61026 says
"every feed reader in the universe supports both. Their functionality is
essentially identical."

Every feed reader, except the one in emacs/gnus.

j> http://ehp03.niehs.nih.gov/article/feed is ATOM with no RSS available

TZ> On my TODO list is integration with Google Reader and other aggregators.
TZ> I think nnrss is not as useful as an aggregator for most cases, and
TZ> maintaining it in the face of the many broken ATOM and RSS
TZ> implementations is a challenge.

Are you saying that I will have to deal with GOOGLE.COM to read RSS/ATOM
in the future gnus?

Re: ATOM feeds

[Ted Zlatanov]

On Thu, 14 Jan 2010 09:49:45 +0800 jidanni@jidanni.org wrote: 

j> http://www.mediawiki.org/wiki/Special:Code/MediaWiki/61026 says
j> "every feed reader in the universe supports both. Their functionality is
j> essentially identical."

j> Every feed reader, except the one in emacs/gnus.

This is not entirely accurate.  Both RSS and ATOM have many versions and
I've seen many feed readers that don't interpret every version
correctly.  Gnus does not intend to be a feed reader: nnrss is obviously
bolted on, not well-integrated like the rest of the backends.  I don't
claim this is a good state of affairs, but that's where we are.

j> http://ehp03.niehs.nih.gov/article/feed is ATOM with no RSS available

TZ> On my TODO list is integration with Google Reader and other aggregators.
TZ> I think nnrss is not as useful as an aggregator for most cases, and
TZ> maintaining it in the face of the many broken ATOM and RSS
TZ> implementations is a challenge.

j> Are you saying that I will have to deal with GOOGLE.COM to read RSS/ATOM
j> in the future gnus?

I didn't say that.  I think feed aggregators are a valuable service and
Google Reader is one which I find particularly nice.  The aggregator
support in Gnus should be flexible enough to handle other aggregator
services, including ones the user chooses to provide.

Writing and maintaining a feed aggregator is a massive undertaking.
Most of the effort goes not into code but into database management and
user support.  I'd rather let other organizations worry about this than
try to provide it inside Gnus, as nnrss.el essentially tries to do.

Note I don't speak for the Gnus project.  This is just my view and I
haven't written a line of code to back up my opinions.  I am also aware
that the FSF may not want to explicitly support GMail in the Gnus
manual, so Google Reader will probably also come under scrutiny.  I
personally don't believe that using external services is in itself a
loss of freedom but the FSF's position will probably be more relevant to
this discussion.

Ted