Some interesting things I noted in the arrays:
- 'Nix Dawn-of-Time
last_payouttimestamp, assume due tonullvalue?:
"last_payout": "1970-01-01T00:00:00",
- 'Nix DoT-minus-1
max_cashout_timetimestamp:
"max_cashout_time": "1969-12-31T23:59:59",
- Weighting & payout of 5 decimal places
10000:
"reward_weight": 10000, "percent_steem_dollars": 10000,
- Max payout would be nice :D
"max_accepted_payout": "1000000.000 SBD",
- Comment body is truncated @ carriage return (as abstract until loaded)?:
"body": "I wish I had the time to experiment...",
depth and children is interesting, I would've expected depth to be determined by parent/child ancestry & the required rendering intention applied accordingly. Wonder if it's used/intended for anything further? Just seems like it could be used to override an objects natural position, like 'pull-left' to depth=0...
Thanks once again for sharing the field notes of your sojourns in SteemitAPI, I really enjoy them.
Yes - I assume that the Unix epoch dates are simply due to null values in this case.
And the
10000numbers represent two decimal places (i.e.,100.00).That comment body was truncated by me in the interest of brevity (and I added the "...").
depthis determined by parent/child ancestry. The first level comments of a post are depth 1 (i.e., consider the post to be depth 0). The replies of those comments are depth 2, and their replies are depth 3, etc.When rendering, I probably would use nested
<ul>so that I wouldn't necessarily have to worry about the depth, though. I only mention it in case each node was rendered individually and you had to figure out the indent level.Thanks for reading!
Thanks for clarifying, & congrats on the @steemitboard
total payout received award!