We just might have the answer below. Please browse through the FAQ. If you can't find what you are looking for please contact us
See and interact with all your friends and contacts from one convenient view
Quickly drill into each friend and see what is going on in their life!
Easily and securely, with the comfort of 256 bit AES peer to peer encryption, VOIP or chat with friends
Virtually impossible to crack
Securely transfer or share files from your library with your friends
Get a birds eye view of the data your node is processing
Safely share photos of your travels, events, and precious moments with your friends
See the contents of the album or view as a slide show
Completely change the look of the application. Fonts, colors, sizes, backgrounds, etc. All at the whim of your creative genius
Join the solution. Put the problem where is belongs; nicely in your rearview mirror
Project XIII exists to facilitate safe and secure communication between people. AES and RSA keys are used to ensure that data can only be decrypted by the parties that need to have access to it. Data can not be compromised by Data Flow Hub/Server (DFH) intrusions. The people that run the DFH can not see what the data is either. They can only see that people are communicating. Please see this link for a .PDF regarding the data flow of Project XIII. AES and RSA keys are described in paras. 15 & 16. FAQ
Project XIII uses AES keys for data encryption. Project XIII does not know what you are moving around. It can only see the meta data and not the actual data itself. After three days the Data Flow Hub (DFH) will delete the data. The DFH does not have the AES or RSA private keys. There is no way to mine the data to see what you are posting, messaging, taking pictures of, etc. You are ultimately responsible for your own data, and any device it is stored on. If you leave a phone somewhere or someone steals your computer they have access to the data left on it. Please be careful with your devices, and remember that you are in possession of data other users have shared with you. FAQ
Project XIII brings a new wrinkle to the data flow space by not storing data on the server. This creates a much more complex technical solution, but is also much more secure as the data is not stored on a central server. Peer to Peer (P2P) is a great solution if both parties are online at the same time, however, that can be difficult to accomplish. Project XIII defeats this limitation by allowing users the capability to upload their data to a central location. The data is encrypted so it can not be mined. It gets deleted after three days so there is no historical record. The user's friends can download the data anytime during that three days. FAQ
Project XIII for desktop will run on the OSX & Windows desktop and laptops. The device needs to be able to run Silverlight 5. The performance of the application is directly related to the amount of processing power it has available as well as the network bandwidth it has access to. FAQ
The application stores data in the documents\Project XIII directory. FAQ
You can securely share and exchange data with your community of Friends by creating wall posts, messages, albums, events, groups for messaging, and share and transfer files in your document library. The platform offers you the ability the chat and make E-VOIP calls as well.FAQ
Yes. Each device (node) running Project XIII has its own database. That database holds the data that the user has access to. Data flows to and from the local database to the Data Flow Hub (DFH). The DFH holds that data for three days. Friends can then request the data and download it. FAQ
Yes. The database needs to have normal database maintenance processes run against it as it can get fragmented and periodically needs to have all the empty space removed. It is also a good idea to backup the database regularly. FAQ
Yes. The database needs to have normal database maintenance processes run against it. It can get fragmented and periodically needs to have all the
empty space removed. It is also a good idea to backup the database regularly. Project XIII provides the following native tools:
The 'Backup Option' places the database, rememberme.txt (remember login) and the contents of the images directory into a .zip file.
This file is stored in the Project XIII directory in the backups folder. The 'Restore Option' will take the backed up .zip file and copy back into the Project XIII
directory structure the database, the rememberme.txt file and the contents of the images folder.
A Project XIII database from a Windows system can be restored to a MAC system and vice versa.
The 'Vaccuum' (database) process assists with data security, performance and removes empty space from the database.
The 'Rebuild Indexes' option drops the existing database indexes and re-adds them. Over time database indexes can get fragmented. So rebuilding them can be good for performance. Rebuilding database indexes can also fix database integrity problems.
The 'Check DB Integrity' option allows the user to see if the database is functioning correctly. If not the user can try to correct the problem using the above mentioned processes.FAQ
Silverlight does not permit the needed ports to be opened for a Peer to Peer communication. A local local Socket Server was written to take the data from the Project XIII node (device) and forward it to the local Socket Server of the friend that it is communicating with. This allows the Silverlight application to communicate via the Peer to Peer approach. Please see this URL for a diagram of the data flow. FAQ
When you delete a record that you own you are presented with the option of selecting a global or a local delete. The global delete will remove the record from the entire Project XIII ecosystem. The local delete will only delete it from your local device. FAQ
When a record is created in the Project XIII ecosystem it is first created in the local database. That record then needs to get pushed to the Data Flow Hub (DFH) so that other friends can download and have access to it. As the node creates records the 'sync table' gets updated with the information that tells it what to push to the DFH. The local node can be used on or offline. It does not care about network status. When it is online it will start pushing and pulling data. FAQ
Project XIII run on all platforms that will run the Silverlight 5. If you pull out an old dual core processor with a small amount of memory, and install Silverlight, Project XIII will run, but it does not mean that you will necessarily have a good user experience. We recommend that you run PXIII on decent hardware for optimal results. We run on a Mac Mini 2.3 GHz, i7 chip with 4GB of memory, a Windows 8.1 1.73 i7 chip with 8GB of memory, and a Windows 8 Nokia 4GLTE with no problems. We also test on a number of Virtual Machines with different hardware and memory settings. You have a 60 day trial. Try out the application on your device. Make sure you are happy with the performance before you extend your license. FAQ
The AES Key is used to encrypt your data. When your data is moved between devices it is encrypted with that AES Key. You have the key, and the destination also has a copy of that key. When the data arrives it is decoded with the AES Key. For more details about AES keys please see this Wikipedia article. FAQ
The RSA keys are symmetrical. There is a public and private key in each set. The public key is given to the public. Anyone who wants to send a message to a person retrieves their public key and uses it to encrypt the data. The owner of the private key is the only person who can decrypt it. Project XIII uses the RSA key set when exchanging AES keys between friends. See this Wikipedia article on RSA. FAQ
Project XIII does not support dumping a database out and re-importing it into another device via the DFH. You can take a backup from a Windows computer and restore that onto a MAC computer. The application does however, support the idea of 'Pushing' the data stored on your device back to the DFH. This data will then be picked up by your other devices. The best way to keep your devices in sync is to leave them on and logged in to Project XIII. Remember, the DFH deletes data every three days. As long as you log in every three days and allow your device to download (pull) all the data, your devices will be in 'sync'. FAQ
Yes. You can lock the application and it will continue to run in the background. You will have to enter your password to unlock it. FAQ
Currently, the maximum file size is 5 MB. This size will increase as 'data chunking' is written into the application in the future. FAQ
The document 'Library', posts and messages will support any document type.FAQ
The 'Key' icon allows you to automatically retrieve a copy of the AES Key from the given friend without interaction with that friend. The code checks to make sure the user requesting the Key is really a friend before sending the response. The code encrypts the data with the requester's AES Key. This means that the data transaction between the friends is secure. It does not use the system key.FAQ
The 'Friends' screen has a button beside each friend record labelled 'Push.' The 'Settings & Tools' section of the navigation drop-down has a 'Push your Data' option. These options allow you to 'push' a copy of the data on your device out to the DFH. The data is encrypted when it leaves your device, and the normal rules apply when it hits the DFH. There are two purposes for these features. The first is to allow you to move a copy of your friends, pictures, etc. to a new device via the DFH. The second is to allow you to backup another user's data for them. For example, if you are friends with Jim and he needs a data restore you can go to his record on your friend screen, click the 'Push' button, and select the time frame that you want, to push his data back to the DFH. Jim, as well as all of his friends with access to his data, will now get access to that data again for a three day period. [Project XIII is really a giant hard drive. Your data is stored on each friend's device and not on a server.] FAQ
SQL databases are not immune from occasional corruption. This is not usually that can be overcome. The Windows application has a 'Repair database' option on the menu. This will take the existing database, extract out the SQL and rebuilt it. This should take care of the problem. Follow the steps indicated. FAQ
When a user creates a record (post, message etc.) Project XIII looks at the date and time of their local system, and derives the UTC time from that. The record is then passed to the DFH and distributed to the appropriate friends. The friend's system looks at the date on the record (UTC), and converts it to their local time. If either user's system has a problem with their clock the date/time stamp will appear to be incorrect. The DFH does not add a date stamp to the record.FAQ
Not currently. We will be resolving this in a later release.FAQ
If the screen resolution changes the resize window redraws the screen again taking into account the new resolution.FAQ
60 days. After that time period your access to the DFH will expire. You will still be able to use the application but you will not be able to download or upload data to the Data Flow Hub. FAQ
Project XIII is being made available with no fees for the user. Once your license reaches the '7 days remaining' point, your access will be automatically renewed in 30 day increments. Once a stable and appropriate method for online payment is secured, Project XIII will be available for the equivalent of one US dollar per month (USD) and you will have the option of extending your license through the Settings & Tools section of the application. There will be a free 60 day trial period for new accounts, after which time a license renewal will be required to move data through the DFH.FAQ