I have given this problem some thought, and I have a suspicion of what is causing it, or, at least, what is causing the most pressing problem which is that new items don't show up in aggregators after marking existing items read. I think it's because the individual items in the project action log RSS feeds do not have unique GUIDs. Instead the URL of the project page is used for GUID. This works (not properly but at least still functions) for the overall feeds like the update feed, but, for individual project feeds, I think it causes them to be all but non-functional. For example, a new item comes in for a project with a GUID of the project's URL. One marks it read. Now, a new item comes in. Because the GUID is still the same, the aggregator thinks that it is the same item and it should still be marked read. Again, I'm no RSS expert. The above is just a hypothesis. If I'm wrong, I apologize. I'll be happy to continue to try to figure out what is going wrong because I think these new project action log RSS feeds are a wonderful feature and I'd love it if this could be resolved. On a different note, I'd like to suggest that, when clicking on a project link in the RSS feed, that it takes one to the action log of the project page instead of the description. But that's a minor quibble. Thank you, Greg