I would say that it is different thing to state some code in Github, that is possibly ‘work in progress’, as safe in the general meaning of the word. It’s other thing to have audited code and the network up and running. Then it really should be safe in every sense.
This reminds me of an old debate from many moons ago whether SAFE stood for Secure Access For Everyone or would it be Safe Access For Everyone.
This is somewhat of an issue with the move from SAFE Network to Safe Network too.
Acronyms should be capitalized “Safe” has an entirely different meaning to SAFE.
To average Joe, Grandma or kids will browsing the network be guaranteed safe or secure?
Just a thought.
5 Likes
Good point and well made, as usual. Cheers @Josh
4 Likes
Can’t wait! 
12 Likes
The photo is from Bulgaria 
Such will be and the next ones if someone does not donate photos 
8 Likes
They don’t technically need to be captialised BTW.
Laser, Scuba, Radar, Unesco,
They work well in title-case when they do double duty as a common word, especially if that word helps in capturing something of what the acronym is aiming to express … e.g. Navy Seals.
10 Likes
Agreed, it is customary though.
How many people know that laser light amplification by stimulated emission of radiation is a acronym, it could be argued that more would assume so were it commonly capitalized.
The same would go for Safe vs SAFE.
I am not arguing for SAFE though not exactly anyway.
My point is if naming to avoid confusion is the primary objective then in my opinion Safe may do so as much as vault perhaps more due to the larger audience.
Personally I agree with the change to node… but am sad to say goodbye to vault at the same time.
Everyone knows what those are… everyone knows what Safe is too and it is definitely not Secure Access for Everyone.
5 Likes
Thanks so much to the entire Maidsafe team for all of your hard work! Here is my latest meme.
8 Likes
I would say that it’s not an actual goodbye. Not to “safe”, nor “vault”.
From our internal discussions, it seems “vault”, and “safe” will be very useful terminology in the UI/UX conceptual world. Albeit perhaps a bit differently than we’ve seen so far .
What happened is more that we shifted focus of the user interface, from the repos and low level code, to upper layers, where there is ample room to construct a rich conceptual world.
@JimCollinson especially is working a lot on that, and there is really no change in the possibilities and status there, rather I’d say we have some very nice ideas going on, and we are freer now to shape the UX without compromising with the technical slimness, or vice versa.
19 Likes
Thank you for the clarification @oetyng. Very much appreciated! 
Does this ensure that the UI/UIX SAFE conceptuals include the command line interface(s)? Meaning that we still have a safe_cli instead of a sn_cli, and still have a safe_drive to access instead of a sn_drive? I sure hope so… 
5 Likes
I wouldn’t go as far as to say that it ensures, but it’s absolutely within the realm of what can reasonably be done.
The cli and the tooling to wrap/package there is not my forte, but this was discussed. (@joshuef might have some input, he knows more than me about those parts). Regardless; if it’s found to be worth the while I’m sure it’s included.
What I think I can say though is that it’s not immediately prioritized, more that we’ve asserted that we can do that when / if we want / need to. And now we continue with the most urgent things.
In short, I think we will have to see how it unravels, but we are not technically limited by these changes, in our abilities to expose a coherent user interface.
9 Likes
I you are arguing about whether a node should be a vault…why not use “maid”? Oh a maid is a node (or a vault), nice"!
2 Likes
Hey @danda is sn_fs open sourced yet? I can’t seem to find it.
4 Likes
It’s currently an empty private repo, but as soon as @danda puts his code in there it will be public.
11 Likes
Cool, thanks for the reply. Just wanted to peek at it and hadn’t come across it or seen it linked but know it’s based on crdt_tree.
2 Likes
So it will still be fleming —> maxwell —> beta?
1 Like
I believe we could create an app that works like a browser but you can subscribe to certain filters (adult content, swearing, violence etc). SAFE stands for uncensored network and this will be possible for anyone, but besides that for kids or anyone who doesn’t want to see certain things they could join this app that filters those content away. Or you could still unlock it by typing in a parental code.
The app could allow people to flag site by root or individual page. Like safe://root_url or safe://someurl/some_page.
5 Likes
It’s entirely possible to still have and use safe as the command line utility. The naming of features doesn’t have to be changed by the repo naming here. Indeed, in discussions we’ve been moving towards this being a separate concern to some degree.
For example with this repo naming change we’re freed up a bit to find the best ux across the board. We could still end up with safe start vault (requires a node under the hood) or safe start farming (which also requires a node under the hood).
15 Likes
