You read Blue Sky Radio's "Now is a good time for a Radio Community Server diaspora."

Now experience the poem.

After the one legged chair?  

Memo to John Robb:

Dear John.

This outage is a blip. And an opporunity.

You catch the decentralized part.

Let me push further.

Move people off of weblogs.com.

Push the community outward. Fledglings from the nest.  

One path among many...  

1. Increase the Radio Community Server population.
   • Bundle with every new Radio download.
   • Download to all Radio users as an update.
   • Goal: hundreds of RCSs.
      
2. Make each RCS more viable.
   • Let each Radio join many RCSs, one as prime.
     • Consolidate weblogs.com updates from multiple RCSs.
     • Change Radio > RCS relationship to Category > RCS. Including comments.
   • CoffeeMug subscription to an RCS.
   • Self-test application: "Is my computer ready to host an RCS?" checking for dynamic IP assignment, free disk, connection speed.  
      
3. Add MetaRCS features.
   • Weblogs.com for the community of RCS sites. Numbers, velocity, freshness of membership.
   • Subscribe to updates from peers; pass throughs appended to your own list. 
   • Redirection, passed on to member web sites. An RCSmaster plans an outage or discovers reduced capacity. Let members know and offer an option to redirect to another RCS.
   • Peer support. Add RCS mirror features, sharing capacity, improving uptime.

Make the RCS the stabilizing platform it's meant to be.

Set them free.

The mailStory macro for manila is brilliant.

Radio and manila need a mailItem macro, scoped to the newsItem instead of the story. Consider reflecting a truncated item title into the email subject.