The great thing is that is now there, and beeing tested repeatedly! 
Run a close-group-5 testnet already!
There something great there, if you manage to aim at simplicity while going up in hierarchy of decision; typically the opposite happens, and complexity creeps in. A binary decision coming from a complex system equals trouble - all IMO obviously…
Thx 4 all the hard work Maidsafe devs
Testing ThePriceIsRightNet was really fun, can’t wait for the next tesnet.
Really great progress, just a matter of time before the big bang
Keep hacking super ants 
I continue to see great progress and the areas being tested are getting more and more advanced! 
However, I feel that I understand less and less how the network is supposed to work, so I am looking forward to the Primer and I think that if the community had a chance to see how SafeNet currently works after these numerous changes, maybe there would be more testers…?
To the team and the community who are participating in the testing, great respect and a big thank you for a great job! 
I’m just waiting on hole punching. 
It would be interesting to get a bit better understanding where the problem lies with QUIC, and with hole-punching in general. Is it in Maidsafes yard or in Libp2p’s, so to speak?
I mean there’s this milestone in Libp2p for example, that has a PR from @bzee waiting to merged, but in unspecified future, together with other breaking changes. Is that something that’s necessary for hole punching to work? Is it possible to get any guesstimate when that release would be released? If it’s like several months, are you going to just wait for that, or maybe code up something for yourself?
Is the the libp2p capable of hole-punching in some other projects? If so, why not with Safe Network?
Right now in other languages, namely go (it’s default).
We want it in libp2p where it belongs and all projects can then use it.
It’s all a question of resources and priorities.
So right now we are working hard to get our algorithms and designs exactly correct, small and secure. That’s where our focus and skill level is. If we have to get into networking, then it’s a distraction, albeit an essential part to get going.
Hope that helps, it’s never a simple answer, but SAFE first libp2p and networking second as networking is a solved problem, SAFE is not. (well not implemented)
It’s not possible to use that go -version with your Rust -coded Safe Network stuff, until the Rust version becomes available?
In software everything is possible, but doing that would be a major distraction. Go is a garbage collected language. Not great for low level libs, so it would mean probably a C ABI interface and then down that rabbit hole. It’s just more distraction and SAFE algorithm is not fully implemented or tested yet.
Thank you for the heavy work team MaidSafe! I add the translations in the first post 
Privacy. Security. Freedom