As Block.one recently announced the feature-complete pre-release of EOSIO. Moving all our code over to this latest version has been our priority over the last few weeks. The transition is now complete and we are beginning the integration testing for our pre alpha release.
I will keep the inSpace Overview section for a few more posts as I think its helpful for new readers.
inSpace is a social filestore. An IPFS filestore running on EOS that has a social layer ontop of it. inSpace uses isCoin (yet to be released EOS based crypto currency) to power the system, reward content, and enable users who stake coins to get either more filespace or receive staking rewards.
Apart from being a distributed social filestore, our main differentiator is that we are developing a spatial user interface, for interacting with inSpace. This means that some normally easy things to do with UI are much harder for us, They take both more dev time and design consideration. But we believe its time for something new, and the effort is worth it.
Our initial implementation is zooming 2D, we will start add in the 3rd D as soon as we get the 2D to a satisfactory base level.
Here is some other early inSpace demo stuff , note the video player does not work so well yet, so its better to download any video files to view them (with the drop down menu on a node).
Upcoming milestone. "inSpace pre alpha running on EOS"
- An inSpace website, where you sign in using your inSpace account, and then provide an EOS identity via Scatter. Your EOS account has the root folder's IPFS address in a Filespace EOS contract.
- The web client can fetch your Filespace tree from IPFS, display it as a force graph, you can upload files to the inSpace server (an IPFS node).
- Cross platform Sync clients working on the IPFS node similar to the web client. Keep improving platform syncing from here forward.
- SamanG core server and web client,
- DaveV cross platform sync clients.
- Servan K Creative director for the project. Hold the long term vision
and make sure the yet to be implemented design hangs together with it.
Production and status reports.
Development update summary
We are beginning to integration test the various parts of our EOS based pre-alpha. This includes getting the basic functionality for OSX, Windows, IOS and Android clients all file syncing with the IPFS filestore. The new release of EOS set us back a little as we needed to get up to speed with code changes and code breaks that came with it. But thats out of the way now and we have our own EOS Dawn 3 server up and running that we can test against. We are ready to move over to the Dawn 3 EOS test net when it is live.
Here is more technical detail on what we got done in the last fortnight:
"I ported the filespace contract (took a lot of trial and error because there was no documentation at the time). Created a private Dawn 3.0 testnet on a new Amazon EC2 instance. The web app is able to communicate with the testnet using the Dawn 3.0 branch of eosjs, to do things like fetching blocks.
I'm working on the backend/frontend architecture and code repository structure. Also Scatter now supports Dawn 3 so I am integrating Scatter with our app"
"Got the android version up and running. There are a few things left to do, and one lock-up left to fix but the basics are up and running now so can start to think about how it looks / is used.
Waiting on a new iPad to finish getting the iPad version running. it looks / acts close to the android version."
"working on the iScoin crypto draft spec for public posting and website update, will need to wait for final EOS coin specifications to finalize, but will publish an early draft here on steemit before and we can refine it with peoples feedback and final EOS coin spec"
Main opening right now is for a front end developer/designer who can
work with Servan to flesh out the front end experience.
Finalizing our repo structure preparing the server and web client
source for GitHub.