I would like to caution a bit against the auto proxy or at least warn users. By sharing the same browser and protocol (HTTP) there are CSRF concerns that can be triggered from the public web. Similarly unprotected pages on the safenet side may access public web resources. I would at least strongly encourage the safe launcher’s proxy to have options to set CSP headers (I know this is just a demo, I am just warning because people attacking Tor were able to do deanonymization by tying things from the public web to the user, granted this was more through services the Tor user was using inside the Tor browser).
Great work! I look very much forward to the messaging API being available via the launcher API to implement my app idea (might I suggest web sockets instead of traditional HTTP or long polling?).
Mine keeps trying “Registering…” 
It doesn’t run on my machine. I run debian 8 64 bit.
I extracted the safe_launcher. I click the safe_launcher icon. Nothing is running. So I did so in the terminal, and nope…
cd safe_launcher
./safe_launcher
No such file nor directory
sh safe_launcher
safe_launcher: 1: safe_launcher: ELF: not found
safe_launcher: 1: safe_launcher: Syntax error: word unexpected (expecting ")")
Some links to surf:
Try restarting the application and register one more time please
Fantastic - well done and thank you all at MaidSafe. Now, to continue my special role as PITA…
ARM?
Only worked when I ran as administrator
Not sure if this is the idea for final client, but keyword didnt make much sense to me as I dont really know what it means and what it will be used for. May confuse the average user
Yeah, it’s a bit like “username”, except it is never used on SAFE as a username, so that’s not a right name either…
It keeps registering forever here (ubuntu 64 bits).
Polo trollbox is going nuts…lol!
Funny stuff!!! Poloniex | Cryptocurrency Exchange | Buy & Sell Crypto Currency
Can not wait to get home and try it out!!! I will be putting Mario Bros and Pacman up to play along with a test video of HD video handling. woohoo!
Yip quite right - we will be releasing / deploying soon and looking at GitHub - japaric-archived/rust-everywhere: SUPERSEDED by https://github.com/japaric/trust
You can see the binaries there 
We will help with ARM for sure, I need it badly for a sample I am working on. I do it manually and Vinicius uses a raspberry PI to test on so we will definitely be OK. Hope to move ARM to teir 1 as well.
IM IN!
Woooo.
But as @filipehdbr notes, the password pin etc is a bit of a pain to fill out. Tell me the conditions in advance of me making mistakes, please!
(but also, alphanumeric?!: xkcd: Password Strength I think we can do better)
I had the same on Windows 7/64. Just restart the whole process and try again, that worked for me.
Would be improved in the next release. Even we felt the same, just because of the time constraints we couldn’t improve it this time. Thanks for your feedback
I agree, PIN / KEYWORD / PASSWORD needs a description field to know when they are going to be used. What’s the difference between PIN and PASSWORD and what is the KEYWORD for?
Fastest way to having all of your IQ sucked out of your brain is to read the Trollbox.
rad. I have to say though. Blown away. I’m stoked there’s electron here (which means I stand a chance of being able to form a coherent PR!). And I like how the proxy gets around the browser plugin issues!
Amazing work everyone!
I’m making a safesite now WOOO…