Yahoo’s lack of commitment to Delicious and other services is enough of a scare to really start to think about resiliency in the cloud.

Adam Curry on Personal Cloud Services

Adam Curry has a good post on why the cloud is problematic if it is under someone else’s control. Therefore DNS is a key service chokepoint. We are taking this seriously and will be rolling out his suggestion of a YOURLS-based (open-source) url service.

The Open Source Cloud Software

Open Source and Free, as nature intended software to be. Aka the most secure option for the source we run is open source licensed and openly (freely) available.

• Scuttle Delicious-like multi-user bookmarking
• Yourls URL shortening service

DNS/Domain Security

There is an issue with losing a domain name due to terms of use from certain domains, e.g., the .ly domain where the single page domain was deemed unethical and illegal and was seized without notice.

Likely the three main generic TLDs .com, .net and .org are the safest zones.

Resiliency in the Graph

Not sure about how to do this but OPML files of Microformats or something like that. There are geeks on this one.

Resiliency in the Data

Here we are happy to do other people’s cloud as a primary service, but need to have the data backup as well as a system that can detect and heal its links and functionality when the public cloud services fail.

Flickr and Data Resiliancy

The use of CC-BY data from Flickr should allow for copying and using the data from a private cloud. The following are the functions that should be supported:

• Detection of use of Flickr data, including data licensing (CC-BY, own copyright, etc.)
• Automatic backup (in various sizes) of the image and video data and metadata
• Plugin cutover on non-availability of given image or entire service to private cloud-hosted data and metadata

Um yeah, we’ll get right to work on that.