Submitted by Robert (not verified) on 3 August, 2007 - 17:29.
I love the Clipperz service.
My questions has to deal with continued availability. If I spend a bunch of time to input data into the system, how can I ensure that the service will be there a year from now? Obviously, I can download a local copy regularly to protect myself.
Here’s the deal. Clipperz doesn’t have contact information for it’s users. This is a real selling point of the service.
As a result, there is no way for Clipperz to send out an email warning users that the service is going away and to instruct people to pull down their data.
One idea might be to allow users to subscribe to some sort of company news list, which is separate and apart from the user list. This might be confusing to people.
Continued Service Availability
I love the Clipperz service.
My questions has to deal with continued availability. If I spend a bunch of time to input data into the system, how can I ensure that the service will be there a year from now? Obviously, I can download a local copy regularly to protect myself.
Here’s the deal. Clipperz doesn’t have contact information for it’s users. This is a real selling point of the service.
As a result, there is no way for Clipperz to send out an email warning users that the service is going away and to instruct people to pull down their data.
One idea might be to allow users to subscribe to some sort of company news list, which is separate and apart from the user list. This might be confusing to people.