Released 0.2.2, which fixes slate publishing for bts >= 0.9.0

voted for you and added you to my slate. The amount of energy you are bringing in is very refreshing, keep it up! 

  voted and added you to my slate

Do you have a demo side etc. where some interested voters or delegates can have a look, without the need to install all the stuff?

I was thinking of making the install of my seed nodes + bts_tools public, so people can have a look at it, but haven't gotten around to do it yet. It would indeed be a good showcase of what the tools can do.
In the meantime, there are some screenshots here (not as interactive, but hey ) : http://bts-tools.readthedocs.org/en/latest/monitor.html#screenshots

Released 0.2, which includes the following changes:

* now requires python3.4
* API CHANGE: format of the config.yaml file has changed, and you will need to update it.
  Run "bts list" and it should tell you what to fix in your config file. For more details,
  see: http://bts-tools.readthedocs.org/en/latest/config_format.html#nodes-list
* added support for building DVS and BTS client >= 0.9.0
* added support for building PLAY client (pls)
* internal refactoring and modularization of the monitoring plugins

The important thing here is that you need to update your config.yaml file. The tools should tell you what to update, but if you're not too sure, just delete your config.yaml file and restart the tools so that they generate a new, valid one for you.

In particular, make sure that you specify the "missed" and "network_connections" plugins in your monitoring list, as they were done automatically before, but you now have to specify them explicitly. See http://bts-tools.readthedocs.org/en/latest/config_format.html#nodes-list for more info.

Quote from: wackou on March 28, 2015, 08:46:51 pm

Quote from: kenCode on March 28, 2015, 06:59:17 pm

The coders here are absolute genius.
The professionalism in the community, the mumbles, bitshares tv, just the language used here in the forum is so refreshing.
I'm luvin it. ™

  well said. These are also the reasons that, regardless of the price or the market cap, keep me excited to no end about this project and why I'm here for the long haul, too

And your claims are backed by... "wishful thinking"? I would have to disagree on the quality of development. Toast is the only one on the Dev team I have really high respect for. Dan comes a close second, but I think his stubbornness has actually impacted the growth of this ecosystem negatively.

When the price is down, there are no interesting forum posts, or things seem a bit on the quiet side, I usually go to the github page and look at the source code and the discussion threads on the github issues, and I immediately regain all confidence in the project. As a c++ coder myself, I regard the BitShares source code as one of the highest quality I have seen in a c++ project. People shouldn't forget that it's been less than a year since BitShares was officially released, and even though some bugs still need to be ironed out, and some optimizations performed in order to provide a stunning user experience, the basic design is really strong and the one that makes most sense to me as of right now in the crypto scene.

Dude, I wish you good luck, but I've seen people with your level of enthusiasm when the price was almost 5 times the current level, and they are not happy campers now.

Just word of advice - don't go crazy all in, you may regret it more, than regretting not going all in.

As said, I'm more excited by the technology that I see being built under my eyes than the immediate profit I could have made by investing in a promising project. So even if the price goes down now, I still believe that if I am right about the project, it will eventually go up again because of its vastly superior technology (maybe a naive point of view, but I want to believe it). In any case, thanks for the advice, but as I should, I only invested as much as what I could afford to lose, so no worries there

Using wackou's bts_tools (run command) I don't think you don't see the actual stdout of the client.

You should definitely see stdout using "bts run" (as well as stdin, you wouldn't be able to open and unlock the wallet otherwise). I think that for the chain sync to kick in, you need to resync the whole blockchain. Try the following:

bts run -- --resync-blockchain

If your config.json contains a chain server correctly configured, then it should use it.