oooooooh - this is me not reading what i downloaded xD
Hmm weird, I altered the link to the drafts page. That should work, we have had some issues today with github. Anyway these links should get the launcher now.
Something odd happening to the CSS on my usual suspects… I can’t make it out.
The source code looks ok, so it doesn’t appear corrupted, yet all three of these appearing as if the CSS isn’t working.
http://hello.safenet
http://eye.eye.safenet
http://yvette.safenet
They should all be centred… no changes made to them since last time. Is that just me or something odd happening?
3 Likes
Think I have run out of money…, will re register
2 Likes
I’m uploading the Linux 64-bit launcher, one moment.
I see the problem:
2 Likes
Uploading files works. Displaying my website only shows the text, though: http://music.audity.safenet/ (on clearnet, content shows up correctly).
1 Like
thanks you’re my hero 
(i’ll compile the source in parallel because i’m impatient ^^ ps: -.-" downloading dependencies and compiling takes so much time >.<…)
Right now the link’s just pointing to all releases in the OP.
Still no joy.
Can you please try again. Github reverted these to draft and travis was publishing again ? very weird. Should be OK now.
2 Likes
I see it now: Releases · maidsafe-archive/safe_launcher · GitHub
2 Likes
binaries are back =)
2 Likes
Success!! thanks dirvine!
Also half way through building a local release. Ha. (Would that have worked?)
2 Likes
Possibly, but we had soo soo many last minute fixes today that I cannot be 100% sure 
Nah
[19:54:53] Starting 'release'...
[Error: Module did not self-register.]
BUT. I’m uploading with the demo app. ALLES GUT.
I see if i try to run a second safe_vault instance on the same system, I get a ‘not supported’ error logging and this second instance stops. This is as promised for this test.
But also the /tmp/safe_vault_chunk_store directory, created and filled by the first safe_vault instance has been removed (not visible at least). As extra punishment, I suspect.
1 Like
It’s one of the bugs we did see on release of this test. It will be fixed, but I would restart your vault now just to be sure 
Thanks for that one.
2 Likes
big red to-mate-O 
1 Like
I see that the network is called “2016_06_28_test_network_5”
Destructive test? Was it already destroyed? says “waiting for establishing connection”