Feedburner specifically has a weird way of dealing with feeds.
feeds. is what sites link to, and has a human viewable feed witha bunch of annoying adverts for different feedreader services.
The actual feed is at feeds2, but DW can parse feeds as well, although the FX direct subscription won't work (if you copy the feeds. uri into the box on DW it'll do it though).
There is an issue with identical content feeds getting different URIs, and that's not something that DW itself can, I think, deal with, LJ has it as well.
It gets worse on some services—Wordpress blogs have an atom and an RSS feed. There are 6 different ways the same content can get syndicated just witha basic WP setup: blog/feed blog/feed/ blog/feed/atom blog/feed/atom/ blog/feed/rss blog/feed/rss/
I was going to submit the error page for name already existing as a bug, miss_s_b had created our mutual friend mark_pack_feed's feed using a different WP feed to the one I'd got, I cared not, I just wanted him on my reading page.
So I'll do that tomorrow unless someone tells me it's already a known bug.
no subject
feeds. is what sites link to, and has a human viewable feed witha bunch of annoying adverts for different feedreader services.
The actual feed is at feeds2, but DW can parse feeds as well, although the FX direct subscription won't work (if you copy the feeds. uri into the box on DW it'll do it though).
There is an issue with identical content feeds getting different URIs, and that's not something that DW itself can, I think, deal with, LJ has it as well.
It gets worse on some services—Wordpress blogs have an atom and an RSS feed. There are 6 different ways the same content can get syndicated just witha basic WP setup:
blog/feed
blog/feed/
blog/feed/atom
blog/feed/atom/
blog/feed/rss
blog/feed/rss/
I was going to submit the error page for name already existing as a bug,
So I'll do that tomorrow unless someone tells me it's already a known bug.