The Current State of Interact (2018)


Although I have been (and am) using it daily, from a dev point of view Interact’s been on the pastures since my boy was born. All that time has given me an opportunity to re-evaluate… everything.

Interact on the desktop

Interact started as a secure graph database for mobile devices. I then added a desktop client, which logically led to a third component – secure store/forward -based data synchronisation across devices.

That in turn led to the realisation that that’s the business model – sync. As a service. Specifically, zero-knowledge synchronisation that doesn’t just sync encrypted data, but also hides meta data. An example where this might be of use is where two journalists need to collaborate on a story about human rights abuses in a country that persecutes such journalism.

In that scenario the only meta data visible to an observer is that someone is making calls to one of my servers. Nobody would know what data is being synchronised, and nobody would know that that data is being shared with another.

That use case doesn’t mean I’m throwing out my existing client apps. It does mean that my client apps should be open-sourced so that people can verify that client-side encryption has been implemented. Also, that others can use my code to create their own clients that need to securely sync structured and unstructured data.

And last but not least, to complete the stuff I started back in 2014 – multi-user and multi-app sync, and server replication (sync) to provide the availability/service continuity I want.

More information

Home | Blog | Photos | Contact | About and all content copyright 1995-2019 by Michael Wittenburg, unless otherwise stated.
All content on this site is licensed under the Creative Commons license, unless otherwise stated. uses a single session cookie because it's required by the tech underlying the site (Microsoft ASP.NET). The cookie stores no information and seves no functional purpose.