Is nrs still working?
safe nrs create --link newname "safe://hyryyry6194d5jy1uihfc6kugjyngnzjoo4etfh1qtzhafrh9bsuts1bc8onra?v=0"
Doesn’t do anything.
(Not expecting an answer til well after Xmas!)
Try with swapping the order of --link and the nrs name you wanna create, i.e.:
safe nrs create newname --link "safe://hyryyry6194d5jy1uihfc6kugjyngnzjoo4etfh1qtzhafrh9bsuts1bc8onra?v=0"
8 Likes
Duh - new brain for Christmas please. Have a good one @bochaco!
12 Likes
So, I gave it the whisky test, which is simply me after a Lagavulin behaving like a noob…
and it works 
I saw no memory leak but note above “Known Issues” does suggest “Over time a node’s memory use continues increasing”; so, unclear what time that is over or against what activity. I uploaded a fair clutter of files and folders trying to trigger it but it just looked simple and stable.
In case useful for encouraging others to try, the abc I noted on this first pass was feeling a bit easier than the readme atm:
# Linux Mint
# clean start with ~/.safe/* removed and ./.config/ random legacy removed
$ curl -so- https://sn-api.s3.amazonaws.com/install.sh | bash
$ safe auth install
$ safe node install
# $ safe auth -V #optional
# $ safe node -V #optional
$ safe node run-baby-fleming
$ safe auth start
# $ safe auth status #optional
$ safe auth create --test-coins
## in future expect to use $ safe auth unlock --self-auth
## but had already done
$ safe auth
#in alt terminal
$ safe auth reqs # gives [Request Id]
$ safe auth allow #[Request Id]
##
# ready to put files.
# later to stop node and close auth
safe node killall
safe auth stop
using safe files put and cat works as normal.
I’ve not looked to use sn_fs just yet.
Questions thrown
- is is possible to have multiple safes unlocked?
- the put of files is not fast… I wonder that’s my setup here being an external drive and also unnecessarily encrypted but unclear what the strain on that is, I wondered might there be an option at some fast secure transfer to another node that has hardware to match that task better than the average?.. if someone was in a rush or on weak hardware, could they pay for that as a service even??
I couldn’t break it and I couldn’t find bugs 
So, I’ll resort to most minor trivia!..
1. wrong version in node -V sn_node (0.25.18)
$ safe node -V
safe-node 0.17.0
2. messy error where auth not started, rather than a nice prompt to user
$ safe auth create --test-coins
Passphrase:
Password:
Sending request to authd to create a Safe...
[2020-12-26T20:00:45Z ERROR safe] sn_cli error: [Error] AuthdClientError - Failed to create client endpoint: [Error] ClientError - Failed to read certificate from '/home/safe/.safe/authd/cert.der': No such file or directory (os error 2)
3. Browser throwing clutter to terminal
when the browser is made available, I wonder if there’s a way to suppress depreciated warnings, as it looks like unfortunate clutter that might confuse user.
$ ./safe-browser-v0.18.0-beta.1-linux-x64.AppImage
(node:28691) DeprecationWarning: file property is deprecated and will be removed in v5.
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false". It will change to be "true" in Electron 9. For more information please check https://github.com/electron/electron/issues/18397
(node:28691) ProtocolDeprecateCallback: The callback argument of protocol module APIs is no longer needed.
20:33:44.684 › url must be a string
17 Likes
I noticed the memory issue when GETting a largish file (50mb) and also when syncing a folder that had a large number (20+) of items in it. It happens consistently and sometimes uses up all the machine’s resources necessitating hitting the off button. And yes, PUTs and GETs are quite slow at the moment.
12 Likes
I wonder 50MB is huge… it that not close to a known artificial limit???
I just tried 20.3MB which is the largest I’ve used previously; put and cat and had no issues… haven’t tried multiples files yet.
5 Likes
@maidsafe small details, but in the nrs I can register these
safe://allcaps and safe://ALLCAPS
This is more for fun 
2 Likes
l w0nd3r th4t caps could be hightlighted in some way and allow this.
“hello” and “heIIo” are not the same but humans are easily confused
It’s more usual to use the Unicode confusables tables to exclude characters that might be mistaken.
https://www.unicode.org/Public/security/8.0.0/confusables.txt
4 Likes
I get an error when sending to a Public Key, I can see why, but I don’t understand why the Public Key is interpreted as SafeKey? Hmmmmm maybe because your only suppose to send funds to a SafeKey…
eddy@hal9000:~$ safe keys create --test-coins --preload 1534
New SafeKey created at: “safe://hyryyyyrsiijxt6expdts5fek3dnicfpewsfiqqq4msc3cu5et7pcdgt49e”
Preloaded with 1534 testcoins
Key pair generated:
Public Key = 96ad52f8f90f68e36d950ac8c55615a8a58b5739da5d99964f688f5ac19a3afa
Secret Key = e508cd2fd4dbbcff2d26cc1edc453b1722d102303463eedf9827775aa624982d
eddy@hal9000:~$ safe keys create --test-coins --preload 1534
New SafeKey created at: “safe://hyryyyyfrw9xmsfhtwkd74ggkeu7bds38axsj4jyfqefm1as79k7ibnq1rc”
Preloaded with 1534 testcoins
Key pair generated:
Public Key = a4a7debb1791a287dd18ca44fa11db27c3ec9d2405720ab962ddfabb5089d223
Secret Key = 668dc1aa771a5e394c7b9ffc2e3e5ff5cc55f120065cce31b2dbcc8b0db90c40
eddy@hal9000:~$ safe keys transfer 1.00000001 --from e508cd2fd4dbbcff2d26cc1edc453b1722d102303463eedf9827775aa624982d --to a4a7debb1791a287dd18ca44fa11db27c3ec9d2405720ab962ddfabb5089d223
[2020-12-27T14:59:01Z ERROR safe] sn_cli error: [Error] ContentNotFound - Content not found at safe://a4a7debb1791a287dd18ca44fa11db27c3ec9d2405720ab962ddfabb5089d223
eddy@hal9000:~$ safe keys transfer 1.00000001 --from e508cd2fd4dbbcff2d26cc1edc453b1722d102303463eedf9827775aa624982d --to safe://hyryyyyfrw9xmsfhtwkd74ggkeu7bds38axsj4jyfqefm1as79k7ibnq1rc
Success. TX_ID: 0
Sure problem solved by sending to the SafeKey, just don’t understand why I can’t send to the Public Key?
I did a few rapid transactions 50x, but sometimes it still takes over 10 secs. Yes even after this and 11 nodes running
Nevertheless super fun trying to break this stuff, hope to see somebody do gb’s uploads, still didn’t figure out how to do uploads myself 
btw don’t mind if the answer follows in 2021. Cheers 
Wow just wow, Maidsafe devs updating is so simple and easy even a clueless consumer can do it 
13 Likes
Will give this a crack soon. Thanks folks. Merry Christmas too.
7 Likes
This was just not implemented, so we should be able to enable that in future versions.
8 Likes
Currently not, but we can work on things like that in the future if we all see the benefits. Right now we are trying to adapt all the front-end apps (CLI and authd) to this new (much simpler) concept of clients and applications simply using a keypair to communicate with the network, i.e. removing any abstraction like account or log-in/out which doesn’t really exist. As you see now we have the authd to manage a Safe, so it can already be seen as a software/app to manage/administer your keys…which eventually could be replaced by a hardware wallet…if I’m confusing you, all I’m saying it’s like a transition phase on front-end from old account/log-in to simply keypairs.
13 Likes
Hey, anyone out there testing the network, how many sections have you seen in your tests? Just curious.
2 Likes
I just gave it a quick try, it’s functional already, we should be able to include it in next release: https://github.com/maidsafe/sn_api/pull/667
12 Likes
Ask and you shall receive! 
nice @bochaco
8 Likes
I created 2 sections, but for that I had to modify some code:
- reduce the number of elders (5 => 3) and the recommended section size (10 => 6)
- always allow a joining node to be adult
I had to try several times because a split doesn’t occur when section is not well balanced. But at fourth attempt with 14 nodes a split finally happened.
Logged in the 3 elders of first section: Running as Elder: ProcessElderChange { prefix: Prefix(0), key: PublicKey::Bls(b2ba61..), elders: {1e007f.., 30ef52.., 6700b8..} }
Logged in the 3 elders of second section: Running as Elder: ProcessElderChange { prefix: Prefix(1), key: PublicKey::Bls(a93953..), elders: {ca6aa1.., cb2bde.., d62f4e..} }
But after the split I cannot connect a client anymore. Probably I am playing sorcerer’s apprentice and I don’t really know what I am doing.
14 Likes
Just keep doing it and noting what works/doesn’t work.
If in doubt , flail blindly, drink more coffee but never give up.
I would love to join in this fun but circumstances…
4 Likes
Nice one.
There’s a bunch of us refactoring some of this exact part. Right now nodes are not giving clients the correct info for the section they should be in. A few other wee niggles, but we are on that one. We had duplicated some logic in sn_node that routing already does well. So we are making that change now.
13 Likes
vdash looks useful
Perhaps blue could be cyan and more easily readable?
Noting that there are then two instances useful
# for all the baby nodes
vdash ~/.safe/node/baby-fleming-nodes/*/sn_node.log
# for the additional node
vdash ~/.safe/node/local-node/sn_node.log
… as below I don’t know if local-node should be local-nodes plural and captured.
1. toggles=?
only by guessing I note that < and > toggle through the nodes which is nice but could be made obvious
… are there other key=options?
Passing thought, I wonder /*/sn_node.log tempts a summary page - sum or averages??.. and usefully perhaps detail of the number of sections… no idea atm where to look for that.
2. RUST_LOG=?
your Readme tempts
RUST_LOG=safe=trace
where above suggests
export RUST_LOG=sn_node=trace
I don’t know if that is different.
?no activity on the additional node (not nodes?)
but trying that more than once I wonder tempts that it’s only creating again what exists?.. same log file at least … and then no activity.
vdash suggests “agebracket unknown” - I wonder this additional node then is not connected.
Should safe node join not be spawning numbered instances additional to the first 11?..
2 Likes