There currently is a running discussion in multiple diaries about the value of motherships in the context of liveblogging, based on the introduction of groups in DK4. Great points have been raised on the advantages and disadvantages of motherships. However, I think the discussion on motherships is looking at a symptom as a opposed to the real opportunity.
Liveblogs do not have a common platform.
Clearly, the events in the world constitute are happening at a rapid pace and in many instances require a liveblog to keep up with real-time information within this community. In some instances, the Front Page becomes the location of choice. In other cases an individual user or group initiates the liveblog.
In all cases, it is left up to the author to come up with the process for creating and managing the liveblog. Creating a standardized process and platform would eliminate many of the questions that are being raised.
Why is a liveblogging platform needed?
In his diary, Please Land The Motherships, Mark Summers makes some strong arguments for eliminating motherships from the Liveblog process. Instead, he recommends using the new groups function in DK4 . However, there are some key requirements that I do not believe the groups feature as currently designed will not support. I am interested in finding out other point of view on this topic.
To accomplish this, I think it is critical to understand the requirements for liveblogging before finalizing a solution.
Here is starting list of requirements that I have been able to gleen from the commentary on this topic over the last two days and my experience over the years with liveblogs.
1. Liveblogs should drive real-time breaking information to one location/clearinghouse.
This concept has been debated heavily. The opposite argument is that if a topic generates enough attention that multiple on topic diaries make the recommended list, so be it. The counter argument is the mothership concept was embraced by the community as a way to consolidate information and the wisdom of the crowd in this decision should hold significant weight. There is value in one-stop shopping when information is coming fast and furious.
2. Liveblogs for major events should have higher visibility than diaries.
With breaking news, many people come directly to DKos to gather information and discuss. In other instances, those who have not had a chance to follow in real time want the ability to "catch up". All user types should be able to utilize and learn from the liveblogs, not just logged in users, or power users. This would not negate the opportunity for other diaries using the standard process to be developed and make their way to the recommended list.
3. Liveblogs should be standardized to enable rapid ramp-up, execution.
This is an easy one. There have been enough liveblogs over the history of this site to allow the group to come up with a common process and template for initiating and managing a liveblog.
4. Liveblogs require collaboration by owners beyond what is available in the comments section to eliminate information overload.
This should be self explanatory. Livebloggers need the ability to manage the blog in a far more active manner than a typical diary due to the influx of data.
5. Liveblogs can require a higher degree of sourcing and editing in real time.
This is a sub-requirement from the prior item. The pace of data coming in creates an opportunity for inaccurate data to be propagated in rapid fashion. The platform needs a way to keep this information accurate. (See Wikipeedia).
6. Liveblogs should enable access to real-time information in the most efficient manner possible.
Self explanatory.
7. The liveblog should be accessible to all users regardless of hardware or bandwidth constraints.
One of the main rationales for the mothership/ROV concept was to keep the discussion moving even after a substantial amount of comments. The Liveblog platform should maintain this feature.
This is just a quick list. There are likely many other requirements. And there are likely requirements that differ by user type, but I wanted to put some basic ideas on the table. Before simply redirecting liveblogs to the group feature, I think it is important to make sure the actual goals of the liveblog capability are well understood. We should then make sure the group blog enables these features.
Here are list of features that I believe would exist in an effective liveblogging platform. There are not intended to be a list of must haves or cover everything. They are simply a list of potential ways to meet many of the requirements outlined above. Some ideas were identified by others during the discussion in the other diaries, some are my own.
1. A common location to access liveblogs on the front page.
H/T to Jim P. One of the first issues is that this discussion attempts to fit liveblogs, which have their own behavior and needs into the current feature set. While this has some issues as described above, one of the features that could be utilized is the community spotlight to highlight active liveblogs with heavy activity. This would eliminate one of the concerns of using the recommended list to try to maintain visibility and the related processes. Alternatively, the featured widget or a new widget/section could be created to highlight liveblogs.
2. A mechanism for recommending or promoting liveblogs outside of the standard recommended list process.
One of the biggest issues being raised is how mothership diaries impact the recommended list. This could be resolved by giving liveblogs and motherships their own recommendation process, depending on how they are featured on the front page. This would be important in situation where many liveblogs are active.
3. An independent blogroll, instead of the diary author's.
The blogroll should be used to highlight key sources of information in liveblogs. Currently, the author's blogroll shows up which may or may not be relevant. This also allows the diary body to be used for key updates.
4. A headline RSS feed maintained by the mothership captain.
The mothership concept would still exist as a clearinghouse/one-stop shop. Within the mothership and ROV, a RSS feed would provide key headlines and updates from news sources.
5. A twitter feed for key hashtags.
Similar to the above, a twitter feed for key hashtags by trusted sources could be maintained by the liveblog owner. Again, opening up space for key content in the body.
6. A collaboration platform for meta to redirect meta discussions.
I am not sure what platform exists today in groups, but a collaboration mechanism outside of comments should exist for meta and organizing. I suspect something beyond emails and PMs would be a good idea.
7. A live video window for key real-time updates to be managed by the captain. (NHK for this, Spill Cam for BP event, AJ Live for Iran/Egypt Protests etc...)
There is no reason users should have to open multiple tabs/windows to follow real time events. Obviously, the featured could be disabled based on hardware and bandwidth.
8. A mothership template for consistency
One of the biggest complaints. If the mothership or liveblogs in general had a standard template and naming conventions, a lot of confusion would be eliminated. This discussion proves that the lack of consistency is creating noise within the system.
9. A standard timeline feature for key updates with links.
One of the values of the mothership is that is provides history. A timeline feature would allow anyone to join in the discussion and understand the basic timeline of events.
10. Automatic rolling over of diaries or a show number of comments feature to manage the number of comments in any one diary.
One of the primary purposes of the Mothership/ROV concept was to keep the amount of comments in a diary manageable and viewable by low bandwidth users. This should be solved through technology, if possible. A new "ROV" could be published or queued based on comments in a liveblog. Alternately, a simple flag limit displayed comments could be utilized. I personally like the new diaries as they create an opportunity for new content and momentum.
That is just a short list of the top of my head. I am sure there are lots of good ideas out there.
This is a topic definitely worthy of discussion. As a non-user of groups, some of these capabilities may already be enabled, and I would love to hear about them. This main purpose of this diary is to push the discussion forward. Regardless, I want to thank all of the people maintaining live blogs. It is time consuming and sometimes thankless. I want to make sure everyone recognizes the effort and time people put into these long lived diaries.
The floor is yours.