Developer delegate: dev.bitsharesblocks

[xeroc]

Our pr manager killed bitshares?

We need to tell the CEO!

[cass]

@svk one of your processes that fill the delegates database seem to be broken .. I can't find any of the bunkermining delegates

Hey guys, I just posted this tech support question and was told to notify this thread, so here it is:
https://bitsharestalk.org/index.php/topic,16344.msg209004.html#msg209004
 
Please and thanx
  -ken

Both questions are related, Ken you broke the backend script that updates the delegate info with incorrect json in your public data field. favdesu also has some reaaaally strange fields in his json that made it impossible to update the mongo database. I pushed an update that removes incorrect fields so it's working again now.

If you want the backend to pick up your delegate.description etc fields you need to use proper json, not "delegate.description"

 

[svk]

@svk one of your processes that fill the delegates database seem to be broken .. I can't find any of the bunkermining delegates

Hey guys, I just posted this tech support question and was told to notify this thread, so here it is:
https://bitsharestalk.org/index.php/topic,16344.msg209004.html#msg209004
 
Please and thanx
  -ken

Both questions are related, Ken you broke the backend script that updates the delegate info with incorrect json in your public data field. favdesu also has some reaaaally strange fields in his json that made it impossible to update the mongo database. I pushed an update that removes incorrect fields so it's working again now.

If you want the backend to pick up your delegate.description etc fields you need to use proper json, not "delegate.description"

[kenCode]

Hey guys, I just posted this tech support question and was told to notify this thread, so here it is:
https://bitsharestalk.org/index.php/topic,16344.msg209004.html#msg209004
 
Please and thanx
  -ken

[xeroc]

@svk one of your processes that fill the delegates database seem to be broken .. I can't find any of the bunkermining delegates

[svk]

You probably get feedback like this frequently, so you may already be aware of this. I'll tell you what I've noticed and let you do with the info as appropriate.

I just updated my delegate client to version 0.9.1, yet the delegate info tab on bsb reflects 0.9.0. I verified the client did publish the new version, yet it is not reflected on the bsb website.

Do you employ a cache for certain info considered to be less dynamic and more static in nature, or have recent code changes in the client (I noticed the cmd "blockchain_is_synced" no longer exists) introduced this behavior? 0.9.0 was the previous version the delegate published.

No cache for that no, I'll have a look but seems strange, did you update using wallet_publish_version?

[Shentist]

do you know this site?

http://www.coincadence.com/charts/

i like how the information is presented. Maybe some charts etc. you can do also.

[Thom]

You probably get feedback like this frequently, so you may already be aware of this. I'll tell you what I've noticed and let you do with the info as appropriate.

I just updated my delegate client to version 0.9.1, yet the delegate info tab on bsb reflects 0.9.0. I verified the client did publish the new version, yet it is not reflected on the bsb website.

Do you employ a cache for certain info considered to be less dynamic and more static in nature, or have recent code changes in the client (I noticed the cmd "blockchain_is_synced" no longer exists) introduced this behavior? 0.9.0 was the previous version the delegate published.

[svk]

Price ratio and fees are not shown in market order history 

Thanks, it was due to the 0.9.0 upgrade changing some fields, it's fixed now.

[clayop]

Price ratio and fees are not shown in market order history 

[svk]

Just a heads-up that there will be some downtime this evening, I tried to do a graceful upgrade to 0.9.0 but the client ended up randomly deleting the chain folder so now I have to resync everything

Everything should be fine now, but do let me know if you notice something not working, there were a lot of hidden changes in this new version..

[svk]

Just a heads-up that there will be some downtime this evening, I tried to do a graceful upgrade to 0.9.0 but the client ended up randomly deleting the chain folder so now I have to resync everything

[kenCode]

Hey svk
Just a thought; It would be cool if on this page (http://www.bitsharesblocks.com) we could click on a little chart icon like this (http://simpleicon.com/wp-content/uploads/bar-chart-7.png) which will popup a simple chart showing the "NEW USERS" statistics, allow us to (jQuery?) scale it, etc.

[svk]

Building on my work on the market page of the wallet, I've made some changes to the Bitsharesblocks orderbook:

Firstly I'm now colorcoding the different order types the same way as the wallet, so bids are green, asks red, shorts blue and covers yellow.

Secondly, both expired cover orders and margin called orders are now added to the Bids table as well as the depth chart. Expired covers use the call price, forced covers are at call price + 10%. This should make it a lot clearer what's actually going on with the orderbook. To see it in action the bitBTC market is currently the best one, as it has forced and expired covers at the top of the orderbook: http://bitsharesblocks.com/asset/orderbook?asset=BTC. I do intend to add scrolling to the tables shortly, I just didn't have the time this morning.

Thirdly, I've made sure the dates you see in the tables are in your local timezone, previously they weren't correctly handled.

[svk]

Hey @svk31,

can I have a API for get the results of

Code: [Select]

blockchain_list_address_balances <address>so that I can fetch data about an address from bitsharesblocks.com?

Sorry been a bit busy working on the wallet, I'll have a look at adding this.