Thanks a lot for the vote of confidence. Did you have anything in mind in particular?
Best regards,
syntaks
A few projects instantly lept to mind, depending on future plans.. A question, is the character limit fixed or is it going to be larger? If it is going to be larger I would very much like to create a decentralized tamper proof github for people that are worried about distributing code that has been tampered with (trojans)
Another obvious one is a torrent site mirror, either public or private.
Is there any information detailing the security models or encryption that is put (will be put) into place? I would very much like to use pgp or some other strong encryption method to control access rather than password protection which is a little messy to manage.
With proper caching, I assume this could be used for a very high traffic application? This would allow for really fast clustering from various geo locations, not having to share sql or anything if I am correct?
From the demonstrations so far it seems you are targetting more of a turnkey blog user, is this going to be only for 'noobies' or will we be able to build on top of this to create "advanced" applications from scratch using the technology? (robust api etc)
1. The character limit is going to be increased on several services. Using r3d to distribute code or code snippets would be easy to accomplish. What we've been doing along the path of development is testing, over and over again. Once the final numbers are set we're going to attack the network in our environment to ensure scalability and response meet our standards and methods of mitigation.
2. Mirrors of all sorts could be a possibility with r3d. Import functions are actually underway to make pulling data in and storing it on the r3d network as easy and efficient as possible.
3. Yes, we're using 3DES for encryption before the data is sent to the blockchain with gzip for compression. PGP and key-based encryption is also something we're experimenting with and once we've come to the consensus via testing that it's ready for production, it will be deployed as an option.
4. It can absolutely be used for a high traffic application. By the design of the storage and delivery, it's just a matter of choosing which method of output you'd like to use to incorporate the data in your application. As I've mentioned, we're using an additional datastore library that's shown thus far itself to be incredibly quick and efficient - with a very small footprint. It's very, very robust as well supporting many useful features. We have what's become the de facto standard leveldb as well. They only co-exist to determine if we're going to completely swap leveldb out or not. In either case, the classes and connectors for both are coded for all of the same functionality so that a swap could be made seamlessly if the decision to swap completely was made. You would literally have a uniform, reliable, data store regardless of location so positioning of an application would be much simpler in terms of scaling than by means of the traditional approaches.
5. We're not targeting anyone in particular, that's just to demonstrate how r3d functions, how it could be used for that application (since blogging is pretty popular) and as demos for use cases are ready for publishing we're providing them. There's virtually no limit as to how advanced you'd like to get when building using r3d. Everything you could need output-wise and so forth is built into the core. We're also supplying our own classes for you to include in your applications aside from the ones we provide templates for. The fact that everything is open-source and readily available for developers such as yourself will make collaboration easy and bring new concepts to fruition in a faster manner. We not only accept requests and suggestions, we encourage them. We're here every day, full-time and those who do have other jobs not directly involved in the majority of development work from home so availability is at maximum.
If you have any other questions, please don't hesitate to ask. Thank you very much again for your support and interest.
Best regards,
syntaks