Infinite Social Media feedback loops

Automated publishing mechanisms, like RSS, Twitter, Facebook and, soon, Google Wave are great innovations. They are used to make people communicate better. But maybe they can also potentially be service killers.

Feeds could be configured into infinite loops: An item is published on a blog-site, which triggers an RSS feed post, which is published on twitter, which is published on the blog-site mentioned earlier, etc... and there you have your loop. And this is a fairly elaborate example. One could think of one to many or many to many publishing mechanisms, causing the feedback loop to grow exponentially in each iteration.

Now take this last idea and create some publish-subscribe patterns using multiple publishers and subscribers whom all feed on eachother. How would this affect processing of the service you are using? Could this be a web2.0 variant of the DDOS attack, one without the need for compromised machines? If one simple loop causes all sites to continuously use up some resources for all services, then maybe a complex loop can bring down the weakest service in the chain.

With the growing number of media feeds people can create and subscribe to, the chances that a feedback loop is created by accident is growing. People are also continually exploring the limits of social media... The only thing we don't know (yet) is who will be the first to create a loop.