He is writing in the context of the journalist-as-curator era we are entering, in which the gatekeeping and even authenticating roles are in some question, and the role becomes one of consuming, editing and presenting more personally.
But Scoble has hit the wall, which means the rest of the pack has long since done so, because he lacks the tools for the job. His seven-point advice would make a developer prosperous.
His points (and my interpretations in parentheses):
1. Curators need to bundle. (Is there a tool to package the most relevant 10 Tweets? No.)
2. Curators need to reorder. (Is there a tool to take someone's package and place new emphasis on some components? Not really.)
3. Curators need to distribute their bundle. (Is there a way of combining the elements you want, then sending them across networks? Not exactly.)
4. Curators need to editorialize. (Part of the value of the new editor is the added value of commentary, but is there is a tool to easily do that?5. Curators need to update. (The ability to take the package and revamp it isn't going to be addressed by the blog; it needs more dynamic firepower from software.)
6. Curators need to encourage participation. (Widgets to build the audience into the creation aren't around.)
7. Curators need to track the audience. (Tools aren't there to give real-time audience measurement and to understand particularly who they are.)
As journalists morph into curators, Scoble offers some clear imperatives for the industry serving them.