Quote from: Tobo on September 07, 2015, 11:38:00 PM

I wonder if it could be a good idea to show a meter on the landing page of the gui client to show the progress of the downloading.

A download queue is planned. (And sort of exists already in 'siac'). Won't be immediate though we've got other things that are high priorities.

Quote from: robinson5 on September 08, 2015, 03:10:25 AM

Hi I'm very excited about the new release! I downloaded it and when I first tried to open it I got the message:

siad errored: Error: spawn ./siad ENOENT

Does anyone have any suggestions? I didn't get a passphrase and am using a mac. I'm worried about losing coins so I don't want to mess around with it myself. All my coins are still in the 0.3.3 wallet. Thanks!

It looks like we screwed up the mac build. I'm surprised you're the first person to have that problem, I guess most everyone else has been running siad in the background. Fix sometime in the next 72 hours.

Quote from: jwinterm on September 08, 2015, 12:29:19 AM

No way to change data directory for UI wallet?

No, right now the data is just going to be in whatever folder you run the UI from. The UI is portable though, so you can put it on whatever drive or logical volume you desire.

Quote from: chrysophylax on September 08, 2015, 03:44:05 AM

taek ...

a screen shot of an open wallet? ..

there is nothing more - it looks like a normal open wallet ...

completely updated and synced ...

i can access all the features of the wallet - but NO password was given - NO access to the 'new' passwords were given after siad was stopeed and the wallet.json file deleted ...

i can see a great deal of work has been put in to the wallet also - fantastic ... but im having a few issues i dont know how toresolve ...

is sia still 'portable' - ie everything contained in the same folder? ...

#crysx

Sia is still portable just like before - all files are contained in the same folder. We're hoping to have a password fix soon. Also, I'll be filling out the FAQ to cover the wallet initialization process. Sorry that you are having troubles.

Quote from: Zer0Sum on September 08, 2015, 03:45:03 AM

Even though I've used about a dozen command line wallets like the cryptonotes, etc...
I've been completely unable to get a wallet working with 4.0 or 4.1 or the GUI on Win7.

- siac "encrypts" your file with a 29 word phrase, then won't accept anything in "Wallet password:"
- so it's basically impossible to unlock your wallet
- the GUI "encrypts" your wallet with a 15 word phrase, but there is no way to unlock it
- there are no wallet.dat files anywhere, just a wallet dir with 3 files

Dude, we are not storing nuclear launch codes here... it's a freaking alpha wallet with maybe $10 in it...
If I want my wallet open and unencrypted how is that your business.

So you are going to compete with FREE CLOUD STORAGE when people CANNOT TRUST THEIR WALLETS Huh

Sorry you are having trouble. The password creation process had some buggy css, some people were unable to view their wallets.

Though the GUI says '15' words, it really means '29'. You unlock the wallet using the 29 word passphrase that is presented to you after wallet initialization. In the updated GUI, we've adjusted the dialog so the message is more informative.

Wallet is not a 'wallet.dat' file, it's a 'wallet.json' file. I know that's different from most projects, but there were some good reasons to use json instead of a different encoding. Since it was in json, naming the file 'wallet.json' made sense.

People asked for encryption on their wallets, it was one of the most heavily requested features. You might only be using it for $10, but a lot of people are planning to back up more data than that. Sia, long term, aims to be an enterprise product. Having top-grade security is important, and a cryptographically secure passphrase is a good place to start. You are not supposed to memorize the passphrase, nor are you really ever supposed to type it in manually. Words are used to make it easier to read and copy down. If we just used a bunch of hex characters, or some encoding like base58, the error rate on copying to paper might be a lot higher.

=======================

For people having trouble, we are continually updating this document: https://docs.google.com/document/d/1zNpAct53E_5p4KO3_-ZOrg5N9HQw8ACTQ7zAyksSIf8/edit