|
Title: Infrastructure Idea: A global, distributed, encrypted database Post by: ripper234 on January 02, 2012, 02:27:05 PM http://www.reddit.com/r/bitcoinideas/comments/nzl6g/a_distributed_persistent_encrypted_database/
Title: Re: Infrastructure Idea: A global, distributed, encrypted database Post by: kangasbros on January 02, 2012, 03:05:51 PM No need to be encrypted IMO - the user can use client-side encryption if he wants.
One application similar to this would be a global content delivery network, in which everyone who has some kind of server running and internet connection can participate. To earn bitcoins with your server/computer, you would just install a client. A central service would control the clients, and sell them to whoever wants to buy some capacity. Title: Re: Infrastructure Idea: A global, distributed, encrypted database Post by: ripper234 on January 02, 2012, 03:08:47 PM No need to be encrypted IMO - the user can use client-side encryption if he wants. One application similar to this would be a global content delivery network, in which everyone who has some kind of server running and internet connection can participate. To earn bitcoins with your server/computer, you would just install a client. A central service would control the clients, and sell them to whoever wants to buy some capacity. I mean that the client libraries should use encryption - you're correct that there are use cases where you might want not to encrypt the data. I think it should be specified and be a part of the protocol - I'd like data written by a Java client to be readable by a python or javascript one. Title: Re: Infrastructure Idea: A global, distributed, encrypted database Post by: kangasbros on January 02, 2012, 03:45:09 PM I mean that the client libraries should use encryption - you're correct that there are use cases where you might want not to encrypt the data. I think it should be specified and be a part of the protocol - I'd like data written by a Java client to be readable by a python or javascript one. One has to think about applications - a content delivery network is mostly used for transmissing big files for very large audiences all over the world. So lot of bandwidth is required, and encryption is not required. Storage isn't needed that much, however bandwidth is. However, for backup usage, where I wan't to store some files in cloud, i need mostly storage. Perhaps both applications (and everything between) could be addressed by the same service. If you need the content delivery function without enryption, you can use the plain service. For backup purposes, client library with encryption could be built, similar to tarspan (http://www.tarsnap.com/). |