It’s 2010. Where’s My Internet Dashboard?

Data needs to live both on my com­puter and in the cloud.

This dash­board of mine should live on a mini server on my com­puter, syn­chro­niz­ing with the cloud when­ever changes hap­pen. My data needs to be portable, it needs to be acces­si­ble any­where, and I need to be able to own it. This means my lit­tle server would syn­chro­nize with servers “out there.” That way, I can still access the ser­vice through mobile devices and library com­put­ers, and every­thing will still be stored locally on my own com­puter. #

Peer to Peer Connections

My con­tact info should exist as my iden­tity on my per­sonal server and when I change any­thing, it should push those changes to my “friends” or what­ever you want to call peo­ple I’ve allowed to have access. This will always go directly to their per­sonal servers, when pos­si­ble, or through the cloud when needed. For larger files, I should be able to “post” them via a secure bit tor­rent feed. That way, every­one in my net­work shares the load of the file. Of course, I should be able to restrict auto­matic down­load of such files to a size limit, much like I do with my SMTP client. #

River of News and Single Composition Interface

The heart of the dash­board will be a river of news, but fil­ter­able in a vari­ety of ways, threaded and com­bin­ing incom­ing mes­sages from all my ser­vices, includ­ing email. A sin­gle inter­face will let me send email, post to my blog or update my sta­tus. It will default to what­ever mode I’m respond­ing to (if it’s a response), but I can select whichever ser­vices I want to push to. #

A Public Face

This would look some­thing like ClaimID, with an OpenID cer­tifi­cate built in and a but­ton allow­ing peo­ple to request access. #