Will there be a tipple or two to celebrate? 
1 Like
Funny, me too!
Should we postpone until tomorrow? Of course, then there is a chance we’ll never meet.
1 Like
Hurry your ass up over already, @Toivo!
Alright, I’ll bite a lunch and I’ll be there as soon as I can. Which will be 13:00. See you soon!
1 Like
But we need roads to get to the place that needs no roads. Or maybe we can fly I guess.
2 Likes
Morning! I believe the cli hanging/failing issue may be resolved, we’ll spend some time today verifying. We’re also using this extra time to make a couple of little improvements, e.g. to logs as we’ve noticed there’s 1 or 2 bits that are not clear enough and would lead to confusion.
We’ll aim for release later today, let’s say around the time of the usual testnet Dev update 
No need to F5 just yet!!
46 Likes
17 Likes
If it all goes to plan, just play the tease and find some lame excuse to delay it till next Monday. You can just imagine the comments
1 Like
Thursday’s are usually fine, that gives us all day Friday to support without having to plead for staff to give up their down time over the weekend. Yes, for a big release like this ideally it would always be closer to the start of the week, but I think we’re all pretty desperate to see how this goes in the wild so it’s certainly worth putting out today. If something was to come up which delayed it until tomorrow then for me that starts tipping the balance towards holding off (EDIT- but that would be for the team to debate if that situation arose).
That’s evil! 
14 Likes
Presumably the test will start with minimal if any data.
If new nodes are allowed when capacity is greater than 50% is breaking my neck trying to first a community node as the network drops a foolish endeavor?
Ie… no new nodes can join immediately?
Yes this will be the case. It’s the bad side of feature complete in some ways. We will not be able to spam the network with tons of nodes and will need to use it and upload data to get the network to grow. Also all data needs paid for so we will give folk free coins on creating accounts etc. So when we look here there will be some shocks, but they are good shocks. I imagine
- This will be unstable, it is literally the first time it all comes together and the wee niggles we have solved in the last days shows where we had disabled stuff or short circuited for our own testing. The main issue is we have limited error recovery here (sync or Anti Entropy), not huge to complete (days), but we decided not to wait on it.
- It will be slow, there is no optimisation at all.
- It will be cumbersome as you need to pay for actions, but not for browsing of course. (we don’t have @JimCollinson ux magic in here yet)
However, it will be the first time any of us see Safe in all its glory, what this will be doing is quite incredible and I believe world changing. This is us launching all Elon Musks first 2 or 3 rockets at once. It will be of that view, explode on impact, but it will fly!
I hope we all can just look, don’t care how unstable, slow or cumbersome, but look and say to ourselves, There! there it is. Today (hopefully) we show the world, this is why we are here and here is our answer to the question Now what are you prepared to do?
The answer, Everything!!!
38 Likes
This is one of the areas we’re working to improve the logs in just now as the user is not informed in their logs why they didn’t get to join. I can imagine a lot of support questions if we leave it like that.
To recap for anyone reading, the network should only allow new nodes to join when it requires resources, so there will be occasions when people try to join but the network rejects them. They will need to try joining again to see if the network is accepting new nodes then. This helps prevent some forms of attack on the network and so will be a vital feature of a live Safe Network.
The nodes that MaidSafe will be putting up to kick off the network will be small, we’re currently testing with 2mb, so it shouldn’t be difficult to fill those up. At the point when the testnet goes live, we will ensure that it WILL need more resources - we will top it up with data to that point so we can test and ensure that we can all join, then we’ll make the announcement.
22 Likes
Is it important which --max-capacity will testers use? Or any should be fine?
2 Likes
Any will be fine, it’s play time and we do need to see what happens when nodes lie about space etc. So do whatever you feel like here. We are getting to the place where we want all sorts of mistakes, attacks and people doing the most whacky things.
However it’s good to set it at the size you are comfortable with.
17 Likes
Tell us what it takes to have a node. I’m crazy to have it … but my computer skills are poor. Some basic guide would come in handy !!! 
1 Like
One wacky thing I wonder about is the effect VPNs might have? A user wanting privacy might get caught in a dilemma of having a SAFE dedicated machine that cannot also avoid being system wide VPN (which seems forced by VPNs); obviously speed would be greatly reduced via VPN and I don’t know if there is a way SAFE can bypass a VPN. I don’t know then how nodes might respond to being bounced around, inadvertently or otherwise.
1 Like
Check out the thread “Quick Start for Farming”. I think.
Will definitely put up a thorough step by step guide at the time of release.
Haha I’m more on the side of “it’s iteration 1 of our new testnet, please be gentle”!
David makes a good point, all these things do need to be tested, but there’s no rush here to go out your way to try and break it IMO.
Let’s see how it functions first under normal usage, iron out the inevitable issues that will rise and make an iteration or two to the testnet, then once the basics all seem settled, that’s the point where I’d like to encourage people to actually try to break it.
19 Likes
Wait, so it’s actually David that’s Robert Duvall.
4 Likes
To know how to break it it is needed to know how it work.
Which means trying to use it.
I do not expect to see many people here who will learn how to break it just by staring at source code for a long time
3 Likes