OK, I’m up: http://test.bluebird1.safenet/
(I got a “already registered” error when I tried to register “bluebird”).
Also:
The demo app connected only after I killed the vault… Not sure if there’s a causal connection.
I had to manually set the pac proxy in Firefox before I could view any sites. Hmm…
I’ve just found a red screen of death… so will post here while it suggests “Could not connect to network!”
Running a local vault, saw very slow performance for registering account… I think that’s my connection then is not strong enough; without local vault works much faster to register account.
Trivial: Upload of website is a bit more fiddly for creating a directory then navigating back and apparently having to retry; finding the folder upload is there and publishing the folder as service but that’s not important atm.
http://www.yvette.safenet - works ok
http://eye.eye.safenet - 4.9MB speed test - works and apparently fast
http://www.knot.safenet - 19.4MB image speed test
Partial downloads: Appeared to upload ok and shows as 19MB in the file detail (rounded down?) but then download appears to fail part way and image detail then suggested it as 11264kB and second attempt 17408kB; so, unclear what is happening there.
I’m back connected… so that red screen passed in ~2mins.
Is ‘the knot’ supposed to be this trippy? 
Is there a special reason for the log not to be ordered on time sent? It feels weird that the times are all mixed up.
Looking good so far 
. Notable improvements since Testnet6:
I’ll keep playing…
Yes I have wondered about that
Could load all three pretty quick , I’m on a limited mobile data connection so it’s not really fast , I estimate 0.5 MB / sec on average , but eye.eye took only 3 secs , so my guess is it may vary a lot . knot was loading progressively at about the before mentioned average speed
I wonder if it sorts it by the time the process finishes (either success or fail) instead of the time it starts, it would explain why failures are at the most recent as they take a longer time to finish.
http://www.knot.safenet is not supposed to skip… that’s a sign that it’s a partial download. In Firefox, right-click.[view image info] to see perhaps it’s not the full 19.4MB.
Did it complete to 19.4MB and smooth unbroken movement?
http://www.hello.safenet
http://www.udhr.safenet
Good impression of this Test 7… happy 
It is a bit broken on my end but my internet isn’t too good.
I tried to download it but it stops at 15MB instead of the full 18.5MB.
Edit:It just took a while but it is fully downloaded (although it is not playing correctly).
One section I got lost in.
I created my public ID no problem.
Went to post website and then followed to the section to manually upload public files. After uploading my website 400+ files successfully I realized I haven’t published the site. So going back to the publish site wizard I could pick a folder, but the main index folder with html pages wasn’t an option. I tried to fix by making a new index, but then couldn’t transfer all the subfolders to it.
Yes, not sure there’s capability to move content atm.
The /public/ appears to require a folder name=servicename, that contains the index.html and from there everything else. If you put index.html to /public/ I suspect it isn’t accessible. I did prefer the previous where it would upload the content of a folder, disregard that folder’s name and create the folder=servicename to hold that content. Going round twice, upload and then publish is an additional step that I suspect will catch people out… but that’s a glitch to polish later.
Perhaps… the Testnet 10 will be the alpha? :3
it runs as smooth as a baby’s bum on OSX ! only issue is having to manually set .pac proxy on browser to be able to view sites…
Is that to suggest it’s destructive or that simply the test will end at some point and content will be lost?
Is the incomplete download of my knot likely due to churn deliberately cutting it off?.. I wonder that’s reasonable and is a non issue because small network where large network would not see that happen.
Maybe we prefer prime numbers 
I hope we don’t need Lagrange’s Theorem or find it’s one of Mersenne’s primes, but we will see. I think it should be in a range findable by Eratosthenes sieve, who knows ?
At first it was loading progressively but remained broken , on the second visit knot remained broken even though a lot of dl mb were reported by the dashboard , then I right-clicked on the file and downloaded the entire thing by saving it to my downloads folder , the Chrome Browser showed 18.5 MB but OSX Finder shows it’s 19.4 MB . Even after downloading it the playback was broken in the browser , and only after reloading the page a third time the whole file got downloaded properly and played back smoothly . kNot-kNOt-KnoT - 3 site visits and a full download to my local folder took about 70 MB of my data allowance on my mobile internet contract if Dashboard reports are correct , so I have to economise a bit thereafter until I reach ADSL Coverage again , no more heavy pages for now - only going for the tiny sites ( indicate them with an 
or an 
)
At this stage we are not focussed on full data integrity or full security. So this is still a network that will try all routes and give up and will also allow small incapable nodes to disrupt data. So we are proving a lot (i.e. all the patents now can be shown to work) and now focus on individual components, hop security next, then data persistence.
It’s looking good though and the steady (frantic in background) pace is good. These tests are perfect ,albeit we are leaning on the community a lot. That will be repaid in full I think though, as long as we keep moving in our determined way.
Great news to see this morning! Will download the binaries and maybe present to lead dev at work as lunchtime entertainment. Wooo!