links
Blog URL /witness-category/@jesta/jesta-witness-update-2016-12-02
Steemit URL https://steemit.com/witness-category/@jesta/jesta-witness-update-2016-12-02
SteemDB URL https://steemdb.com/witness-category/@jesta/jesta-witness-update-2016-12-02
comment model

      Twig Examples:

      {{ post.title }}
      {{ post.author }}
      {{ post.body }}
    
post[id] 1474826
post[author] jesta
post[permlink] jesta-witness-update-2016-12-02
post[category] witness-category
post[parent_author]
post[parent_permlink] witness-category
post[title] jesta witness update - 2016-12-02
post[body] With v0.16.0 coming next week, it's been the focus of most of my attention (alongside of Reprint). It's also been a few weeks since my last update, and I imagine the frequency of my updates through the rest of the year won't improve an incredible amount. This time of year (with the holidays) ends up always being incredibly demanding of time :) ## 1. Accomplished the last half of November: - Helped @charlieshrem with the launch of [geekinprison.com](http://geekinprison.com), a [Reprint](https://steemdb.com/reprint/@greymass/reprint-build-your-blog-or-website-on-the-blockchain) powered blog based on his activity on [steemit.com](https://steemit.com). - Reprint now supports pagination by default and [author pages](http://jesta.us/@jesta). Author pages load an account from the steem blockchain to display information on a custom HTML page. With [today's update to steemit.com](https://steemit.com/steemit/@steemitblog/steemit-com-ui-release-0-1-161202), even more customization options are standardized and those fields will also be included in the near future. These author pages can also have custom URLs by using the Reprint routing configuration, and could even be combined in a custom route to build a "team" page. - I've been working on a new "theme" for the base installation of Reprint, which I'm calling `develop`. The develop theme is built for designers and developers looking to get involved and understand how the data is organized in Reprint. It displays the information passed to the frontend, the site configuration options, and other additional bits of information that should help in crafting a steem-powered website. - [steemdb.com](https://steemdb.com) is now on a much more powerful server, one in which the entire database can actually fit into RAM. This has sped up the site significantly and should allow for growth right alongside the community. - Progress on a steemdb <-> reprint integration has been started, which simply use API calls to steemdb for calls that cannot be completed (optimally) through the steem api. - Testing and upgrades of servers to 0.16.0 (and it's various release candidates). I've build this version dozens of times at this point across a number of configurations, and am almost prepared for Tuesdays's hard fork. My witness nodes are upgraded and I'll activate the block signing on them over the weekend for final testing. - Worked with @arhag to update the [get_ops_in_block](https://github.com/arhag/steem/tree/get-ops-in-block) patch updated for 0.16.0, which he also [issued a pull request](https://github.com/steemit/steem/pull/649) for inclusion into the main repository. This modification to steemd is what allows sites (like [steemdb.com](https://steemdb.com)) to query each block for all virtual operations (such as rewards). ## 2. Upcoming projects/goals - Development on Reprint has been moving slower than we had anticipated, so my primary focus is on it's progress. When we first started building Reprint, we had a very vague idea of exactly what was required to make it work, and at this point the picture is much clearer. - This weekend and into next week, most of my efforts will be in finalizing the 0.16.0 steem nodes powering my witness account, the private server that powered steemdb, the public (US) node behind steem.ws, the private (read-only) nodes for our Reprint hosted sites, and the test servers I have setup for development. - I have slowly started researching what it takes to build plugins directly for steemd, which is foreign territory for me. The documentation is a bit out of date (which is to be expected with a massive change like 0.16.0), but I'm still figuring it out. My hope is that I can build some useful APIs to help the needs of both Reprint and steemdb (as well as anyone else needing similar data). ## 3. Thoughts from this week It's been a little over 3 weeks since my last witness update, and during that time I burned out pretty hard and ended up crashing for a little over a week. Comparing my productivity (and even post history) in September vs November shows a stark difference in how much I actually have been accomplishing recently. I am not complaining or have objectives in addressing this, I just wanted to recognize that this occurred. The one thing I don't want is to leave the impression that I've stopped caring about steem, or even worse, that I'd given up. The situation is far from that, and I really believe 2017 is going to be a banner year for steem. Throughout the remainder of the year, I plan on slowly increasing my efforts again to try and find a happy medium of "productive" and "not working so hard I end up crashing". It's a fine line for someone like myself, who tries to optimize and push the bountries of my work as far as possible. However with the Holiday season rapidly approaching, I also plan to just "go with the flow" of things and not set the bar too high. Burnout is no joke, it's just really easy to ignore when you're excited :) ## 4. Previous update [Update for the week ending 2016-11-11](/witness-category/@jesta/jesta-witness-update-2016-11-11) ### [Finally, don't forget to vote for witnesses here.](https://steemit.com/~witnesses)
post[json_metadata]
[tags]
[0] witness-category
[1] witness-update
[users]
[0] charlieshrem
[1] arhag
[links]
[0] http://geekinprison.com
[1] https://steemdb.com/reprint/@greymass/reprint-build-your-blog-or-website-on-the-blockchain
[2] https://steemit.com
[3] http://jesta.us/@jesta
[4] https://steemit.com/steemit/@steemitblog/steemit-com-ui-release-0-1-161202
[5] https://steemdb.com
[6] https://github.com/arhag/steem/tree/get-ops-in-block
[7] https://github.com/steemit/steem/pull/649
[8] /witness-category/@jesta/jesta-witness-update-2016-11-11
[9] https://steemit.com/~witnesses
[app] steemit/0.1
[format] markdown
post[last_update] 2016-12-03T02:18:51
post[created] 2016-12-03T02:18:51
post[active] 2016-12-22T14:33:00
post[last_payout] 2017-01-03T03:10:00
post[depth] 0
post[children] 10
post[children_rshares2] 0
post[net_rshares] 0
post[abs_rshares] 0
post[vote_rshares] 0
post[children_abs_rshares] 0
post[cashout_time] 1969-12-31T23:59:59
post[max_cashout_time] 1969-12-31T23:59:59
post[total_vote_weight] 0
post[reward_weight] 10000
post[total_payout_value] 43.896 SBD
post[curator_payout_value] 1.978 SBD
post[author_rewards] 278723
post[net_votes] 321
post[root_comment] 1474826
post[max_accepted_payout] 1000000.000 SBD
post[percent_steem_dollars] 0
post[allow_replies] 1
post[allow_votes] 1
post[allow_curation_rewards] 1
post[beneficiaries]
post[url] /witness-category/@jesta/jesta-witness-update-2016-12-02
post[root_title] jesta witness update - 2016-12-02
post[pending_payout_value] 0.000 SBD
post[total_pending_payout_value] 0.000 STEEM
post[active_votes]
post[replies]
post[author_reputation] 71627050027202
post[promoted] 0.000 SBD
post[body_length] 0
post[reblogged_by]
post[html] <p>With v0.16.0 coming next week, it's been the focus of most of my attention (alongside of Reprint). It's also been a few weeks since my last update, and I imagine the frequency of my updates through the rest of the year won't improve an incredible amount. This time of year (with the holidays) ends up always being incredibly demanding of time :)</p> <h2>1. Accomplished the last half of November:</h2> <ul><li>Helped @charlieshrem with the launch of <a href="http://geekinprison.com">geekinprison.com</a>, a <a href="https://steemdb.com/reprint/@greymass/reprint-build-your-blog-or-website-on-the-blockchain">Reprint</a> powered blog based on his activity on <a href="https://steemit.com">steemit.com</a>.</li> <li>Reprint now supports pagination by default and <a href="http://jesta.us/@jesta">author pages</a>. Author pages load an account from the steem blockchain to display information on a custom HTML page. With <a href="https://steemit.com/steemit/@steemitblog/steemit-com-ui-release-0-1-161202">today's update to steemit.com</a>, even more customization options are standardized and those fields will also be included in the near future. These author pages can also have custom URLs by using the Reprint routing configuration, and could even be combined in a custom route to build a "team" page.</li> <li>I've been working on a new "theme" for the base installation of Reprint, which I'm calling <code>develop</code>. The develop theme is built for designers and developers looking to get involved and understand how the data is organized in Reprint. It displays the information passed to the frontend, the site configuration options, and other additional bits of information that should help in crafting a steem-powered website. </li> <li><a href="https://steemdb.com">steemdb.com</a> is now on a much more powerful server, one in which the entire database can actually fit into RAM. This has sped up the site significantly and should allow for growth right alongside the community.</li> <li>Progress on a steemdb &lt;-&gt; reprint integration has been started, which simply use API calls to steemdb for calls that cannot be completed (optimally) through the steem api. </li> <li>Testing and upgrades of servers to 0.16.0 (and it's various release candidates). I've build this version dozens of times at this point across a number of configurations, and am almost prepared for Tuesdays's hard fork. My witness nodes are upgraded and I'll activate the block signing on them over the weekend for final testing.</li> <li>Worked with @arhag to update the <a href="https://github.com/arhag/steem/tree/get-ops-in-block">get<em>ops</em>in_block</a> patch updated for 0.16.0, which he also <a href="https://github.com/steemit/steem/pull/649">issued a pull request</a> for inclusion into the main repository. This modification to steemd is what allows sites (like <a href="https://steemdb.com">steemdb.com</a>) to query each block for all virtual operations (such as rewards).</li> </ul><h2>2. Upcoming projects/goals</h2> <ul><li>Development on Reprint has been moving slower than we had anticipated, so my primary focus is on it's progress. When we first started building Reprint, we had a very vague idea of exactly what was required to make it work, and at this point the picture is much clearer. </li> <li>This weekend and into next week, most of my efforts will be in finalizing the 0.16.0 steem nodes powering my witness account, the private server that powered steemdb, the public (US) node behind steem.ws, the private (read-only) nodes for our Reprint hosted sites, and the test servers I have setup for development.</li> <li>I have slowly started researching what it takes to build plugins directly for steemd, which is foreign territory for me. The documentation is a bit out of date (which is to be expected with a massive change like 0.16.0), but I'm still figuring it out. My hope is that I can build some useful APIs to help the needs of both Reprint and steemdb (as well as anyone else needing similar data).</li> </ul><h2>3. Thoughts from this week</h2> <p>It's been a little over 3 weeks since my last witness update, and during that time I burned out pretty hard and ended up crashing for a little over a week. Comparing my productivity (and even post history) in September vs November shows a stark difference in how much I actually have been accomplishing recently. I am not complaining or have objectives in addressing this, I just wanted to recognize that this occurred. The one thing I don't want is to leave the impression that I've stopped caring about steem, or even worse, that I'd given up. </p> <p>The situation is far from that, and I really believe 2017 is going to be a banner year for steem. Throughout the remainder of the year, I plan on slowly increasing my efforts again to try and find a happy medium of "productive" and "not working so hard I end up crashing". It's a fine line for someone like myself, who tries to optimize and push the bountries of my work as far as possible. However with the Holiday season rapidly approaching, I also plan to just "go with the flow" of things and not set the bar too high. </p> <p>Burnout is no joke, it's just really easy to ignore when you're excited :)</p> <h2>4. Previous update</h2> <p><a href="/witness-category/@jesta/jesta-witness-update-2016-11-11">Update for the week ending 2016-11-11</a></p> <h3><a href="https://steemit.com/~witnesses">Finally, don't forget to vote for witnesses here.</a></h3>
post[html_preview] <p>With v0.16.0 coming next week, it's been the focus of most of my attention (alongside of Reprint). It's also been a few weeks since my last update, and I imagine the frequency of my updates through the rest of the year won't improve an incredible amount. This time of year (with the holidays) ends up always being incredibly demanding of time :)</p>1. Accomplished the last half of November:
post[image]
post[ts] 1480753131
accounts
accounts loaded from the configuration
tags
tags loaded from the configuration
steem configuration
    resources/config/config.yaml - `steem` variable
  
host https://node.steem.ws
blog configuration
    resources/config/config.yaml - `blog` variable
  
theme develop
title reprint powered blog
subtitle blockchain powered blog
elements
[author] 1
[category] 1
[payout] 1
[votes] 1
[comments] 1
filters
[accounts]
[jesta]
[0] post