ATOM User Stream Duplicates My Entries in Google Reader

Question

I have a problem with the ATOM feed that I generate, and the entries are duplicated in the readers.

I designed the C # class to create ATOM feed entries and, ultimately, the complete feed object from my data elements. It complies with RFC 4287 for the Atom syndicate feed format.

The feed is created correctly. It is not currently being tested, as I am adding two non-standard extension elements and have not yet created a suitable namespace for them, but these problems exist even when they are checked.

I also see two different behaviors between my direct Atom feed and the FeedBurner feed.

Here are two channels. http://feeds.feedburner.com/oldtownhome/ http://www.oldtownhome.com/index.atom

I subscribed to both channels through Google Reader and have reports from other users that they see the same problem, but are not consistent with when they see the problem against me.

Problem with feed # 1: Feed items that are currently in the feed (25 input channels) are duplicated randomly. This can be a one-time duplication in one day, duplication of several elements in a few days, or sometimes the entire contents of the feed seem to be “republished” in one day, even if they already exist on previous days.

Problem with feed # 2: Messages seem to be duplicated in random order, even if the entries fall from the main channel (although they can be accessed through other Atom channels on the site, for example, for individual Atom channels).

I ran everything I could think of. I guaranteed that pubDate never changes, every link to the document is unchanged from the moment of publication, a node is added with the actual value and unchanged guid value as the value, but nothing helps. I even made feedburner use my XML in the hope that the problem might have been feedburner.

I am at a loss and hope that others have had a similar situation and have some tips.

Update Perhaps an element related to this, my feedburner sent an email that went through yesterday with Recent Posts, which reported 25 new posts (total in the main feed where it displays this information). Of these 25 posts, 24 were not new and were delivered one at a time in the previous 30 days or so. Only 1 message was new, and it was concentrated at the top along with the rest of the messages.

Is it possible that this is due to some kind of connectivity issue when Feedburner cannot access my feed (because it is something or something else), and then when it is uploaded to Feedburner again, is all the content new? I did not have any extended outages with my server for a year, but you had problems that could last from 30 seconds to 5 minutes.

This is the most annoying issue because Feedburner / Google Reader are both black boxes.

Answer 1

If someone stumbles upon this random entry while looking for duplicate Google Reader solutions, I think I may have discovered the root cause of the problem, and this is annoying.

The blog had many many channels, but only one primary. The primary channel listed the last 25 posts at any given time, but besides this channel, there were other searchable feeds in the content metadata. These included category channels, comment feeds, feeds with specific pages, popular message channels, etc. It seems that Google Reader, in all its wisdom, looked through all these channels and considered them as completely different channels and elements, although they all had the same unique identifier for messages (url for the message). After I deleted all of them as searchable feeds, and also necessarily redirected the main channel without www to www. To ensure that all URLs are unique and not duplicated, it seems that everything is fine with the world, and google reader - no. longer duplication of content.

Well, it has been many months of annoying and frustrating elements trying to troubleshoot a service that is completely unable to debug or provide useful information to the developer.

I hope this helps someone ... someday.