- Dec 31, 2015
- 166
- 526
So I've been unhappy with Core, and verbally supportive of BU and Classic. I suppose it's time I am supportive in deed as well. Walk the walk, as it were.
Yet I have a handful of questions....
These alternative clients (BU and Classic are both under consideration) are based off Core, right?
Are these able to employ the same database data? Like, if I terminate Core, and point (e.g.) BU at the same directory, will it use the same data, or will it want to redownload it all? Then what if I want to switch back? Just stop one, and start the other? Stretch question - what about running them both at the same time on the same data? (Had to ask)
Can I run these alternative clients across TOR in the same manner as Core?
Do they employ similar/identical .conf files?
Can I run Armory atop Classic or BU the same way I run Armory atop Core?
I know - so many questions...
Yet I have a handful of questions....
These alternative clients (BU and Classic are both under consideration) are based off Core, right?
Are these able to employ the same database data? Like, if I terminate Core, and point (e.g.) BU at the same directory, will it use the same data, or will it want to redownload it all? Then what if I want to switch back? Just stop one, and start the other? Stretch question - what about running them both at the same time on the same data? (Had to ask)
Can I run these alternative clients across TOR in the same manner as Core?
Do they employ similar/identical .conf files?
Can I run Armory atop Classic or BU the same way I run Armory atop Core?
I know - so many questions...