I'm not a programmer but I can understand somethings about that. However, I do not know how to use 'mklink / j' or use GUI utilities.
I started to follow your second advise (for me easier to understand). I opened this file:
'Resources / app / js / mainjs / config.js' from Sia program, and in this file I can see some vars, one of these is:
Datadir: Path.join (app.getPath ('userData'), './sia'),
Its value is in "C: \ Users \ UserName \ AppData \ Roaming \ Sia-UI \ config.json"
If I change this value, when I start SIA appears an error.
The error apears with folder moved or not moved.
This error signs to this file: config.json (from 'resources / app / js / mainjs / config.js' Sia extrated program and other parameters).
I think the file with 'Path.join' value is the target, but I do not know which file could content it yet.
Thanks for your answer.
The reason the time is so long is that lots of the drives on our network are spare drives or leftover drives that people are contributing to the network. These drives are essentially free, because they are just lying around doing nothing.
As the network grows, it will eventually outpace the amount of storage that can be provided by idle drives, and the price should go up to something more manageable. ROI of 18-30 months seems pretty reasonable to me.
$30/TB just covers the raw cost of the drive. Add the cost of land, electricity, server racks, etc, and the TCO of a drive rises to probably $60 for 3 years (which is about how long you would expect the drive to last before failing). So the high end of the price is likely to stay below $2 / TB for the lifetime of Sia.