hunterlester: hunterlester: Yes! There’s probably so much that I’m missing that I could learn from you.

I doubt it. I’ve been rather slow in catching up on how to interact with the SAFE rust client libraries, and have a lot more to learn from you and others.

I do enjoy making these kind of interfaces though and have been going about the design of that by making it operate the way I would find most convenient for a working prototype.

Mine is currently running similar to yours, with the rest of the skeleton/scaffold in place, but most functions are non-working. I don’t foresee running the authenticator in another thread to be a problem for full “sssh mode” if necessary. Locally managing multiple accounts in “a SAFE way” has been on my mind. So a lot of work on the different functions has been held back. Each invitation code, account secret, and account passphrase is associated with a given name or alias similar to how things are done for ssh. The idea was to save them to an encrypted file on the local computer that could be opened via the user entering their passphrase only, or a different “safely passphrase”. That way, if their computer became compromised with a keylogger after account creation, then the adversary would not be able to access the account remotely on their own. Not that this really matters in the end, since if your machine gets rooted/compromised you’re done for. That’s why I was spending a little brainstorming time on a SafeOS, wondering if that is a better use of time, since almost Everyone’s OS is easily compromised in some way or another.

hunterlester: hunterlester: Are you designing a whole new terminal altogether? That would be interesting to watch and learn. I think it would be more ideal than my current implementation of simply running a CLI program.

No, just a terminal program for linux or other similar OS. The input/output just mimics navigating the cli on your local linux shell. (I know SAFE is supposed to be for Everyone, but I don’t think there’s any hope in keeping data safe on any closed source OS. I don’t know of many non-linux users (well maybe Mac I suppose) that enjoy playing with a good CLI either…

The plan was/is to proceed in 2 phases, lately it looks more like 4. First get the cli working stable with all single commands (except for mount/umount ) via “–run”, phase 2 would bring in full interactivity or sssh. Phase three puts all of these commands into the rust fuse framework so that mount and umount functions work to enable something like SAFE-VFS (is this what you were referring to @davidpbrown? ). Last, hard or soft links would need to be implemented in order to get the website publishing features working like in the first SAFE-VFS that was written in ruby. This was all supposed to be a big surprise but I think it’s good you brought up the topic. It helps me get motivated. If it turns out that I can’t pull it off for devcon (which is looking more and more likely - so I was looking to devcon to get a lot of what I needed to know to finish this), at least you have the basic outline I’ve been trying to follow for myself. Cheers!