Sorry I missed a whole string of posts yesterday.
I have to somewhat agree with nextgencoin. I have a certification in Computer Networking, specializing in Cisco Systems (Router, Switches, LAN and WAN). I can't even get the wallet to work and so I couldn't mine it, that why I'm focusing on Ethereum and the Eth clones with DAPPS. I've try all in the tutorials, read me's, open ports on my router and machine, and even turn off my firewall. The upnp needs to be added to the wallet, as much as some people will complain of security issues with upnp, but just connecting to the internet is always a chance of a security issue and anyone is naive to think otherwise.
The decentralized storage of this project need to be promoted more effectively. I like it's a working model, but that won't matter if people aren't convinced and trust the security factor of it.
upnp is available in 0.4.0, and so far I don't think anyone has reported problems with it. Upnp does not work on all routers, but having it should be a big step forward. We've also taken other steps to try and figure out why synchronization doesn't always work on the first pass, but we have the following ideas:
1. our networking timeouts are too short
2. we don't have enough bootstrap nodes
3. peer lists are not being pruned properly and some percentage of the time a node will get all bad peers
There may be other problems as well, but I hope addressing the above 3 will fix 75% of the remaining connection issues. That still leaves a few people out to dry, but we're going to keep working on it. All of these solutions should be in either 0.4.1 or 0.4.2.
Right now we have 6 bootstrap nodes, 2 of which are our own. If anyone wants to volunteer to be a bootstrap node, the only requirement is that you forward your ports. You can expect to get more traffic as a bootstrap node, but it shouldn't be a ton of bandwidth.
How do I encrypt/put a password on the wallet? I'm lazy at the moment to look through the whole posting...lol
If you are using 0.4.0, it actually won't let you do hardly anything until you encrypt and unlock the wallet.
Commands:
'./siac wallet init'
'.siac wallet unlock'
You can lock and unlock the wallet as many times as you want:
'./siac wallet lock'
'./siac wallet unlock'
When the wallet is locked, you won't be able to accept hosting contracts, won't be able to mine blocks, won't be able to send coins around. But you will be able to view your wallet balance.
- the option to select multiple files
- a more user friendly gui (the fact that it works with most people is not an argument, I had to open ports and add gateways for it to work = not very user friendly)
- command line only for developer reasons, if you want mass adoption you don't want the majority to have access to something they don't understand. It scares them away.
- the ability to upload files larger than 500MB
- Progress: a solid team working on sia, moving forward in a professional way with enough transparency.
- trust, if you want me to store my files I need to know or at least have the absolute impression that my files are safe. This is a beta, which means they aren't. Most people will likely only store (personal) data with a final product that has had some 'testing', has been reviewed, troubleshooted, benchmarked,...etc.
I will however store some data that is 'a little less important' to get the ball rolling and support this community. Community, also very important!
Keeping in mind this is a beta I know everything needed will be added once it's ready. But you asked, so...
edit: the ability to lock my wallet and make backup directly from gui instead of having to copy it out of the folder.
Might help if you narrow it down to 1 or 2 things that are most important, but if you truly need all of them to start using Sia, then you've given exactly the feedback I asked for
File limit is raised to 5 GiB in 0.4.1
upnp is available in 0.4.0
Slightly more comprehensive GUI available in 0.4.1 (might not be more friendly though - we could really use some help if someone has design+html/css/js experience)
The command line is not meant to be used by everyone, but the GUI is still incomplete in some ways, so people have to break it out every now and then. As we continue development, it will be needed less and less.
trust, if you want me to store my files I need to know or at least have the absolute impression that my files are safe. This is a beta, which means they aren't.
This is something that's going to take both time and development iteration. We've got redundancy set to '6' right now, but especially at this stage I would never recommend using Sia as the only place you've housed your data. If 0.4.1 goes well, I might suggest having 1 local copy and 1 Sia copy as sufficient.