At some point everything we know of SAFE becomes a simple concept, of that which is SAFE and that which is not. That is, the network is considered a platform, on which you are or otherwise are not. The KISS principal of marketing, is rooted in the user does not need to think… and marketing to everyone, is helped by being familiar and then obvious.
I wonder SAFE would benefit from having stated intent for the future of any design, that the UI capability draws on which already exists as most familiar.
So, having a CLI that is familiar, will help adoption, with effort put to WHAT is done and not HOW it is done.
With the suggestion already of
rsync, I wondered that “wfetch” is an odd name, where perhaps that should be the familiar
Could SAFE have a stated intent, that the core CLI commands should be based on what Linux already does.
$ safe cat "safe://bbkulcax6ulw7ovqhpsindkybsum4tusmvuc7ovtr2bu5gj6m4ugtu7euh" $ safe grep -rl 'wfetch' / | xargs sed -i 's#wfetch#wget#g' $ safe wget "safe://helloworld" $ safe ls -1 $ safe ls -B $ safe man safe
To be expected that the CLI already most familiar, follows from Linux rather than random other OS.
A SAFE user’s expectation can then be understood, as simply “that which Linux does - or not at all.”