Well, this is pretty much a very complex idea, but it’s commonly used in software development. I was wondering the usability of it. Maybe I’m just not seeing it right now, but I’m open to the discussion. Every time I have trouble with understanding those high tech, I always go back to the analogous version of the Zettelkasten system. In that case, if you have a new version of an old node, in that case you just write a new one. You can just start at the very beginning of that node to refer back to the old nodes. You don’t have to say all the changes you make for that single node, as long as you’re accumulating those new ideas and creating them together. As long as that process of making things together is evolving, then your system is okay. It introduce another layer of complexity without adding the value that is corresponding to that cost. If we go back to the basic philosophy of UNIX design, keep things simple as possible, then I’ll put a big question mark on adapting this idea in my workflow right now.

What’s your plan for synchronization issues? I mean, lots of guys, it’s going to use primarily a desktop environment and I guess mainly using the phone to have a browser kind of functionalities as primary features. Okay, active test server will get access to synchronize in the future. I saw your information about what’s your plan here? Are you going to use a syncthing or your own version of server?

uconsole, but the waiting time is somewhat Loooong now…