5 posts displayed of 46 total (page 1 of 10).
Account jesta , using activity types [post]
testing, 1, 2, 3!
2017-03-19 | Tags: [spam] [test] [jesta-testing]
links
Blog URL /spam/@jesta/testing-1-2-3
Steemit URL https://steemit.com/spam/@jesta/testing-1-2-3
SteemDB URL https://steemdb.com/spam/@jesta/testing-1-2-3
comment model

      Twig Examples:

      {{ post.title }}
      {{ post.author }}
      {{ post.body }}
    
post[id] 2190119
post[author] jesta
post[permlink] testing-1-2-3
post[category] spam
post[parent_author]
post[parent_permlink] spam
post[title] testing, 1, 2, 3!
post[body] Just a test post for parsing within a concept application.
post[json_metadata]
[tags]
[0] spam
[1] test
[2] jesta-testing
[app] steemit/0.1
[format] markdown
post[last_update] 2017-03-19T18:49:51
post[created] 2017-03-19T18:49:51
post[active] 2017-04-08T10:23:42
post[last_payout] 2017-04-19T19:11:57
post[depth] 0
post[children] 6
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] 0.000 SBD
post[curator_payout_value] 0.000 SBD
post[author_rewards] 0
post[net_votes] 98
post[root_comment] 2190119
post[max_accepted_payout] 0.000 SBD
post[percent_steem_dollars] 10000
post[allow_replies] 1
post[allow_votes] 1
post[allow_curation_rewards] 1
post[beneficiaries]
post[url] /spam/@jesta/testing-1-2-3
post[root_title] testing, 1, 2, 3!
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>Just a test post for parsing within a concept application.</p>
post[html_preview] <p>Just a test post for parsing within a concept application.</p>
post[image]
post[ts] 1489967391
jesta witness update - jan/feb 2017
2017-02-17 | Tags: [witness-category] [witness-update]
links
Blog URL /witness-category/@jesta/jesta-witness-update-jan-feb-2017
Steemit URL https://steemit.com/witness-category/@jesta/jesta-witness-update-jan-feb-2017
SteemDB URL https://steemdb.com/witness-category/@jesta/jesta-witness-update-jan-feb-2017
comment model

      Twig Examples:

      {{ post.title }}
      {{ post.author }}
      {{ post.body }}
    
post[id] 1991157
post[author] jesta
post[permlink] jesta-witness-update-jan-feb-2017
post[category] witness-category
post[parent_author]
post[parent_permlink] witness-category
post[title] jesta witness update - jan/feb 2017
post[body] Checking in and providing a status update since it's been far too long. I have been somewhat inactive (posting) since the Holiday and wanted to summarize the last few months. The reason for the inactivity has been due to multiple very time consuming reasons - with one being a move across the US that started with an unknown destination. A move was needed, that's all I knew. I'm happy to say that some direction has finally been set and decisions made, the move is finally in progress, and I'll be settling down into a new home early to mid March. After settling, I plan on getting back into the groove of things, participating more and being a more active voice. It's also very likely that I'll also be exploring opportunities for remote work to generate some income. I've been living the startup life in Southern California for the last 2 years without a traditional job. It's taken it's toll on me across many, many levels. So what have I been up to since my last update in early December? Here's a brief rundown, I'll try to be brief and not too in-depth. - @paxmagnus and I unfortunately have had to set the business concepts behind Reprint aside for the time being. We spent a lot of time this year really digging into how things can play out, but the overall feeling is "we are too early for this". Development will continue on the open source project, but actually building a business behind it that's able to hire the team we need is going to have to wait for the ecosystem to mature. There's a number of external dependancies blocking it's success which should be resolved as time goes on and I'll continue to advocate. We have been planning a recap post for the @greymass account with the details of this, but my move has really slowed progress on formulating it into a post. More than happy to answer any specific questions about this, but I don't want to keep rambling :) - Created and have continued to work on the [Steem Forum Prototype](https://steemit.com/steemdb/@jesta/steem-forum-interface-prototype). There are some insurmountable problems right now simply because how Steem itself is built, but those problems will be overcome with time and I still really believe there's a lot of merit to an interface like this. The 3rd party access/authorization stuff slated this year on the 2017 roadmap will be a huge help to progress with projects like this. - If you're a regular to steemdb (well, as much as I am), you've probably noticed a lot of small changes over the last few months and a few improved pages. I've been slowly tweaking and adjusting things (like adding links or changing text) to slowly make the site more useful for certain use cases. I'll compile a list of these changes and mark a new version once I've completed everything on my current todo list. Over the past few months I've gotten dozens of suggestions for improvements, and have been slowly working through them all, so keep them coming! - I've migrated a bunch of servers since the beginning of the year to optimize costs. [SteemDB](https://steemdb.com), SteemDB's private steemd node, `node.steem.ws` (public RPC node), [SteemStats](https://steemstats.com), [Reprint](http://reprint.io) (and the handful of prototypes using it), and a few utility servers have all been moved to these new resources. This took a lot of time to find the right homes for each of these services at the right price, but I'm pretty happy with everything landed. - I've spent a decent amount of time over the last 2 weeks troubleshooting my witness nodes and have yet to find a conclusive reason as to why every day or two I'm missing a few blocks. It's been frustrating and I'm still actively monitoring things and I've finally resorted to just setting up brand new servers. All has been quiet for 24 hours and I'm hoping that by posting this I don't jinx it... I am very much hoping things have smoothed out and I can go for a week without missing a block. It would be nice to not worry about it while I'm on the road. - There have been some very spirited debates about curation rewards over the last week or so which I've been involved in. I only mention it because I've spent hours reading posts and comments, and responding as much as I can. A thank you to everyone that's engaged in the debate and helped clarify the issues we're all experiencing. No perfect solution has been found, but the public discourse has been healthy and relatively free of trolling and harsh words. Starting next week, until sometime in March, I'll be in transit. On the road, hotels, and friends spare bedrooms - and I'm uncertain how great the internet's going to be or how much I'll be at a computer. I have tethering via my phone and SMS notifications setup for my witness environment, but if you need something urgent, feel free to use steemit.chat. I'll at the very minimum have email and get notifications from steemit.chat. Here's hoping for a much calmer 2/3/4th quarter of this year! :)
post[json_metadata]
[tags]
[0] witness-category
[1] witness-update
[users]
[0] paxmagnus
[1] greymass
[links]
[0] https://steemit.com/steemdb/@jesta/steem-forum-interface-prototype
[1] https://steemdb.com
[2] https://steemstats.com
[3] http://reprint.io
[app] steemit/0.1
[format] markdown
post[last_update] 2017-02-17T11:06:03
post[created] 2017-02-17T11:06:03
post[active] 2017-02-18T02:47:15
post[last_payout] 2017-03-20T15:39:45
post[depth] 0
post[children] 20
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] 21.052 SBD
post[curator_payout_value] 2.093 SBD
post[author_rewards] 159985
post[net_votes] 286
post[root_comment] 1991157
post[max_accepted_payout] 1000000.000 SBD
post[percent_steem_dollars] 10000
post[allow_replies] 1
post[allow_votes] 1
post[allow_curation_rewards] 1
post[beneficiaries]
post[url] /witness-category/@jesta/jesta-witness-update-jan-feb-2017
post[root_title] jesta witness update - jan/feb 2017
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>Checking in and providing a status update since it's been far too long.</p> <p>I have been somewhat inactive (posting) since the Holiday and wanted to summarize the last few months. The reason for the inactivity has been due to multiple very time consuming reasons - with one being a move across the US that started with an unknown destination. A move was needed, that's all I knew. I'm happy to say that some direction has finally been set and decisions made, the move is finally in progress, and I'll be settling down into a new home early to mid March.</p> <p>After settling, I plan on getting back into the groove of things, participating more and being a more active voice. It's also very likely that I'll also be exploring opportunities for remote work to generate some income. I've been living the startup life in Southern California for the last 2 years without a traditional job. It's taken it's toll on me across many, many levels.</p> <p>So what have I been up to since my last update in early December? Here's a brief rundown, I'll try to be brief and not too in-depth.</p> <ul><li>@paxmagnus and I unfortunately have had to set the business concepts behind Reprint aside for the time being. We spent a lot of time this year really digging into how things can play out, but the overall feeling is "we are too early for this". Development will continue on the open source project, but actually building a business behind it that's able to hire the team we need is going to have to wait for the ecosystem to mature. There's a number of external dependancies blocking it's success which should be resolved as time goes on and I'll continue to advocate. We have been planning a recap post for the @greymass account with the details of this, but my move has really slowed progress on formulating it into a post. More than happy to answer any specific questions about this, but I don't want to keep rambling :)</li> <li>Created and have continued to work on the <a href="https://steemit.com/steemdb/@jesta/steem-forum-interface-prototype">Steem Forum Prototype</a>. There are some insurmountable problems right now simply because how Steem itself is built, but those problems will be overcome with time and I still really believe there's a lot of merit to an interface like this. The 3rd party access/authorization stuff slated this year on the 2017 roadmap will be a huge help to progress with projects like this.</li> <li>If you're a regular to steemdb (well, as much as I am), you've probably noticed a lot of small changes over the last few months and a few improved pages. I've been slowly tweaking and adjusting things (like adding links or changing text) to slowly make the site more useful for certain use cases. I'll compile a list of these changes and mark a new version once I've completed everything on my current todo list. Over the past few months I've gotten dozens of suggestions for improvements, and have been slowly working through them all, so keep them coming! </li> <li>I've migrated a bunch of servers since the beginning of the year to optimize costs. <a href="https://steemdb.com">SteemDB</a>, SteemDB's private steemd node, <code>node.steem.ws</code> (public RPC node), <a href="https://steemstats.com">SteemStats</a>, <a href="http://reprint.io">Reprint</a> (and the handful of prototypes using it), and a few utility servers have all been moved to these new resources. This took a lot of time to find the right homes for each of these services at the right price, but I'm pretty happy with everything landed. </li> <li>I've spent a decent amount of time over the last 2 weeks troubleshooting my witness nodes and have yet to find a conclusive reason as to why every day or two I'm missing a few blocks. It's been frustrating and I'm still actively monitoring things and I've finally resorted to just setting up brand new servers. All has been quiet for 24 hours and I'm hoping that by posting this I don't jinx it... I am very much hoping things have smoothed out and I can go for a week without missing a block. It would be nice to not worry about it while I'm on the road.</li> <li>There have been some very spirited debates about curation rewards over the last week or so which I've been involved in. I only mention it because I've spent hours reading posts and comments, and responding as much as I can. A thank you to everyone that's engaged in the debate and helped clarify the issues we're all experiencing. No perfect solution has been found, but the public discourse has been healthy and relatively free of trolling and harsh words.</li> </ul><p>Starting next week, until sometime in March, I'll be in transit. On the road, hotels, and friends spare bedrooms - and I'm uncertain how great the internet's going to be or how much I'll be at a computer. I have tethering via my phone and SMS notifications setup for my witness environment, but if you need something urgent, feel free to use steemit.chat. I'll at the very minimum have email and get notifications from steemit.chat.</p> <p>Here's hoping for a much calmer 2/3/4th quarter of this year! :)</p>
post[html_preview] <p>Checking in and providing a status update since it's been far too long.</p><p>I have been somewhat inactive (posting) since the Holiday and wanted to summarize the last few months. The reason for the inactivity has been due to multiple very time consuming reasons - with one being a move across the US that started with an unknown destination. A move was needed, that's all I knew. I'm happy to say that some direction has finally been set and decisions made, the move is finally in progress, and I'll be settling down into a new home early to mid March.</p>
post[image]
post[ts] 1487351163
STEEM Forum Interface (Prototype)
2017-01-23 | Tags: [steemdb] [forums] [prototype]
links
Blog URL /steemdb/@jesta/steem-forum-interface-prototype
Steemit URL https://steemit.com/steemdb/@jesta/steem-forum-interface-prototype
SteemDB URL https://steemdb.com/steemdb/@jesta/steem-forum-interface-prototype
comment model

      Twig Examples:

      {{ post.title }}
      {{ post.author }}
      {{ post.body }}
    
post[id] 1817207
post[author] jesta
post[permlink] steem-forum-interface-prototype
post[category] steemdb
post[parent_author]
post[parent_permlink] steemdb
post[title] STEEM Forum Interface (Prototype)
post[body] Over the last two weeks or so I've been fiddling with the STEEM blockchain and what it would look like if it were a formatted like a more traditional forum. Today I'm happy to share the results of this experiment, with the goals of collecting feedback and any ideas related to it you may have. This prototype forum is not finished or optimized, so I apologize for any slowness or strange errors you might run into. A permanent link to the forums experiment is also available in the [**Labs**](https://steemdb.com/labs) section of [SteemDB.com](https://steemdb.com/). You are all free to give it a shot here: [https://steemdb.com/forums](https://steemdb.com/forums) or if you'd like, you can finish reading this post on the forums here: [https://steemdb.com/forums/steemdb/@jesta/steem-forum-interface-prototype](https://steemdb.com/forums/steemdb/@jesta/steem-forum-interface-prototype) ## Features - **Homepage**: Categorizes popular tags into groupings presented on the homepage, giving users a topic based approach to discovering content on the blockchain. If you have ideas for additional forums (and tags) that I'm not using, please let me know! ![https://steemdb.com/examples/steemdb-forums-home.png](https://steemdb.com/examples/steemdb-forums-home.png) - **"First Tag Only" Groupings**: Only the first tag (or category as it's known) is used for placing topics into forums. This prevents posts from appearing in multiple forums and gives more weight to the first tag you choose when writing a post. - **Forum List of Topics**: Under each "forum", a list of posts is displayed and ordered by the most recently active (just like a forum). Replying to a post will "bump" it to the top of that forum, perpetuating the discussions with others. The icons on the page also represent indicators of the posts payout (battery icons), the declining of rewards (star), or it being archives (lock). ![https://steemdb.com/examples/steemdb-forums-icons.png](https://steemdb.com/examples/steemdb-forums-icons.png) - **Posts as threads**: Each post on steemit is displayed as a traditional forum thread, with the author information in the left column and the content in the middle. A right sidebar will likely be added in the future containing meta information about the post. ![https://steemdb.com/examples/steemdb-forums-post.png](https://steemdb.com/examples/steemdb-forums-post.png) - **A summary at the bottom of each top-level post**: This summary contains information related to the original post, as well as a summary of all the information that will follow on the page. Clicking on the "Latest Reply" block will scroll the page to the latest reply. Below the summary is information about when/where the post originated, a link to reply directly to this post, as well as links to view this post on steemit.com and on steemdb.com. ![https://steemdb.com/examples/steemdb-forums-summary.png](https://steemdb.com/examples/steemdb-forums-summary.png?) - **Forum Breadcrumbs**: A trail of links is provided in the top portion of each page to help you navigate backwards through the forums. ![https://steemdb.com/examples/steemdb-forums-forum.png](https://steemdb.com/examples/steemdb-forums-forum.png) - **Flattened Discussions**: Comments are no longer nested, but displayed chronologically in order, with any nesting being shown as "Quotes". You can use the "jump" link to scroll up to the comment which this was a response to. The image below compares the forum (left) to a discussion on steemit (right). The second image shows how the "Read More" button shows the complete text of the quoted post, and the jump button scrolls your browser up to the post that was quoted. ![https://steemdb.com/examples/steemdb-forums-threads.png](https://steemdb.com/examples/steemdb-forums-threads.png) ![https://steemdb.com/examples/quotedposts.gif](https://steemdb.com/examples/quotedposts.gif) - **SteemConnect Integration for Responding**: You can actually reply to threads using this forum prototype thanks to SteemConnect.com. **Disclaimer: Please be think twice about submitting your login information to any website, including SteemDB/SteemConnect. Be safe and keep your account safe, this technology is all very experimental still.** I've personally used the service to leave a few comments already (using my posting key for safety reasons), but your account safety is in your hands. ## Where's this going? No clue. Welcome to the my lab :) In all seriousness, I feel this concept may actually have a lot of merit, and I may integrate this type of data view deeply into SteemDB. It's an attempt at categorization of the information within the blockchain, and attempting to bring it into a perspective that many on the internet are comfortable with for discussions. This is a prototype of what could be, and could be perfected into nearly a perfect blockchain based forum. Some of the code I wrote for this is bad, some of the APIs I had to use to make it aren't designed for it, and the integration for participating on STEEM with the client aren't quite "perfect" yet. So there you have it, a STEEM-powered forum! ## Quick Update not related to SteemDB I just wanted to say "hello" and "sorry I haven't been posting much", life's been very busy (lots of stories). I'm still involved in STEEM related stuff almost every day, I just honestly haven't had the motivation to post a lot lately. I'm always around on steemit.chat if you need to contact me for any reason. But I am still around, and still working on a handful of neat projects. I haven't abandoned anything and am very excited with where we're heading with STEEM in 2017! (Diff testing... sneaky sneay)
post[json_metadata]
[tags]
[0] steemdb
[1] forums
[2] prototype
[image]
[0] https://steemdb.com/examples/steemdb-forums-home.png
[1] https://steemdb.com/examples/steemdb-forums-icons.png
[2] https://steemdb.com/examples/steemdb-forums-post.png
[3] https://steemdb.com/examples/steemdb-forums-summary.png?
[4] https://steemdb.com/examples/steemdb-forums-forum.png
[5] https://steemdb.com/examples/steemdb-forums-threads.png
[6] https://steemdb.com/examples/quotedposts.gif
[links]
[0] https://steemdb.com/labs
[1] https://steemdb.com/
[2] https://steemdb.com/forums
[3] https://steemdb.com/forums/steemdb/@jesta/steem-forum-interface-prototype
[app] steemit/0.1
[format] markdown
post[last_update] 2017-02-11T00:24:33
post[created] 2017-01-23T11:03:03
post[active] 2017-02-11T00:24:33
post[last_payout] 2017-02-23T20:58:09
post[depth] 0
post[children] 55
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] 308.345 SBD
post[curator_payout_value] 23.168 SBD
post[author_rewards] 2171372
post[net_votes] 576
post[root_comment] 1817207
post[max_accepted_payout] 1000000.000 SBD
post[percent_steem_dollars] 10000
post[allow_replies] 1
post[allow_votes] 1
post[allow_curation_rewards] 1
post[beneficiaries]
post[url] /steemdb/@jesta/steem-forum-interface-prototype
post[root_title] STEEM Forum Interface (Prototype)
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>Over the last two weeks or so I've been fiddling with the STEEM blockchain and what it would look like if it were a formatted like a more traditional forum. Today I'm happy to share the results of this experiment, with the goals of collecting feedback and any ideas related to it you may have.</p> <p>This prototype forum is not finished or optimized, so I apologize for any slowness or strange errors you might run into. A permanent link to the forums experiment is also available in the <a href="https://steemdb.com/labs"><strong>Labs</strong></a> section of <a href="https://steemdb.com/">SteemDB.com</a>.</p> <p>You are all free to give it a shot here:</p> <p><a href="https://steemdb.com/forums">https://steemdb.com/forums</a></p> <p>or if you'd like, you can finish reading this post on the forums here:</p> <p><a href="https://steemdb.com/forums/steemdb/@jesta/steem-forum-interface-prototype">https://steemdb.com/forums/steemdb/@jesta/steem-forum-interface-prototype</a></p> <h2>Features</h2> <ul><li><p><strong>Homepage</strong>: Categorizes popular tags into groupings presented on the homepage, giving users a topic based approach to discovering content on the blockchain. If you have ideas for additional forums (and tags) that I'm not using, please let me know! <img src="https://steemdb.com/examples/steemdb-forums-home.png" alt="https://steemdb.com/examples/steemdb-forums-home.png" /></p></li> <li><p><strong>"First Tag Only" Groupings</strong>: Only the first tag (or category as it's known) is used for placing topics into forums. This prevents posts from appearing in multiple forums and gives more weight to the first tag you choose when writing a post.</p></li> <li><p><strong>Forum List of Topics</strong>: Under each "forum", a list of posts is displayed and ordered by the most recently active (just like a forum). Replying to a post will "bump" it to the top of that forum, perpetuating the discussions with others. The icons on the page also represent indicators of the posts payout (battery icons), the declining of rewards (star), or it being archives (lock).</p></li> </ul><p><img src="https://steemdb.com/examples/steemdb-forums-icons.png" alt="https://steemdb.com/examples/steemdb-forums-icons.png" /></p> <ul><li><strong>Posts as threads</strong>: Each post on steemit is displayed as a traditional forum thread, with the author information in the left column and the content in the middle. A right sidebar will likely be added in the future containing meta information about the post.</li> </ul><p><img src="https://steemdb.com/examples/steemdb-forums-post.png" alt="https://steemdb.com/examples/steemdb-forums-post.png" /></p> <ul><li><strong>A summary at the bottom of each top-level post</strong>: This summary contains information related to the original post, as well as a summary of all the information that will follow on the page. Clicking on the "Latest Reply" block will scroll the page to the latest reply. Below the summary is information about when/where the post originated, a link to reply directly to this post, as well as links to view this post on steemit.com and on steemdb.com.</li> </ul><p><img src="https://steemdb.com/examples/steemdb-forums-summary.png?" alt="https://steemdb.com/examples/steemdb-forums-summary.png" /></p> <ul><li><strong>Forum Breadcrumbs</strong>: A trail of links is provided in the top portion of each page to help you navigate backwards through the forums.</li> </ul><p><img src="https://steemdb.com/examples/steemdb-forums-forum.png" alt="https://steemdb.com/examples/steemdb-forums-forum.png" /></p> <ul><li><strong>Flattened Discussions</strong>: Comments are no longer nested, but displayed chronologically in order, with any nesting being shown as "Quotes". You can use the "jump" link to scroll up to the comment which this was a response to. The image below compares the forum (left) to a discussion on steemit (right). The second image shows how the "Read More" button shows the complete text of the quoted post, and the jump button scrolls your browser up to the post that was quoted.</li> </ul><p><img src="https://steemdb.com/examples/steemdb-forums-threads.png" alt="https://steemdb.com/examples/steemdb-forums-threads.png" /></p> <p><img src="https://steemdb.com/examples/quotedposts.gif" alt="https://steemdb.com/examples/quotedposts.gif" /></p> <ul><li><strong>SteemConnect Integration for Responding</strong>: You can actually reply to threads using this forum prototype thanks to SteemConnect.com. <strong>Disclaimer: Please be think twice about submitting your login information to any website, including SteemDB/SteemConnect. Be safe and keep your account safe, this technology is all very experimental still.</strong> I've personally used the service to leave a few comments already (using my posting key for safety reasons), but your account safety is in your hands.</li> </ul><h2>Where's this going?</h2> <p>No clue. Welcome to the my lab :)</p> <p>In all seriousness, I feel this concept may actually have a lot of merit, and I may integrate this type of data view deeply into SteemDB. It's an attempt at categorization of the information within the blockchain, and attempting to bring it into a perspective that many on the internet are comfortable with for discussions.</p> <p>This is a prototype of what could be, and could be perfected into nearly a perfect blockchain based forum. Some of the code I wrote for this is bad, some of the APIs I had to use to make it aren't designed for it, and the integration for participating on STEEM with the client aren't quite "perfect" yet.</p> <p>So there you have it, a STEEM-powered forum! </p> <h2>Quick Update not related to SteemDB</h2> <p>I just wanted to say "hello" and "sorry I haven't been posting much", life's been very busy (lots of stories). I'm still involved in STEEM related stuff almost every day, I just honestly haven't had the motivation to post a lot lately. I'm always around on steemit.chat if you need to contact me for any reason.</p> <p>But I am still around, and still working on a handful of neat projects. I haven't abandoned anything and am very excited with where we're heading with STEEM in 2017!</p> <p>(Diff testing... sneaky sneay)</p>
post[html_preview] <p>Over the last two weeks or so I've been fiddling with the STEEM blockchain and what it would look like if it were a formatted like a more traditional forum. Today I'm happy to share the results of this experiment, with the goals of collecting feedback and any ideas related to it you may have.</p><p>This prototype forum is not finished or optimized, so I apologize for any slowness or strange errors you might run into. A permanent link to the forums experiment is also available in the Labs section of SteemDB.com.</p>
post[image] https://steemdb.com/examples/steemdb-forums-home.png
post[ts] 1485190983
jesta witness update - 2016-12-02
2016-12-03 | Tags: [witness-category] [witness-update]
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
Some UX/thinking around Links as content types
2016-11-20 | Tags: [steem] [steemit] [content-types] [links] [brainstorming]
links
Blog URL /steem/@jesta/some-ux-thinking-around-links-as-content-types
Steemit URL https://steemit.com/steem/@jesta/some-ux-thinking-around-links-as-content-types
SteemDB URL https://steemdb.com/steem/@jesta/some-ux-thinking-around-links-as-content-types
comment model

      Twig Examples:

      {{ post.title }}
      {{ post.author }}
      {{ post.body }}
    
post[id] 1394806
post[author] jesta
post[permlink] some-ux-thinking-around-links-as-content-types
post[category] steem
post[parent_author]
post[parent_permlink] steem
post[title] Some UX/thinking around Links as content types
post[body] There's one specific quote I really want to dive into from [steemitblog's latest post, "Proposed Upgrade for Blockchain Incentives"](https://steemit.com/steem/@steemitblog/proposed-upgrade-for-blockchain-incentives). Specifically this line, towards the bottom under "Different Curation Rewards for Different Content Types": > **Links should not have extremely high author rewards because they are almost entirely requests for curation**. Links as a content type (like posts) - it's something I've been thinking about for a while now, but don't see much chatter about. So I figured I'd write a little bit and potentially stir up some excitement for what this could be. ## Preface Throughout this post I am going to be using a mockup I did for a steemit blog (using reprint), which can be found here: http://steem.reprint.io I will be referring to this site as "blog.steemit.com" in screenshots and code samples, as that's what this site could potentially be someday. I also may be biased towards the awesomeness of this idea simply because I am building reprint, and am willing to admit it :) ## What would a content type of "Link" be? Think about how reddit uses in links to external content on other websites, as content on reddit itself. That's the one line pitch for this new type of content. Reddit has two forms of user generated content: links and selfposts (what a terrible name). They are pretty similar in terms of data, with the one major difference. As you browse reddit, clicking the title of a piece of content does one of two things: - You're taken to a reddit page, with a post someone wrote in a subreddit, it's comments, and other related information. - You're taken off reddit to an external website. Posts here on steemit are what we have now and are just like the first type above. The "link" content type that could be added to steem/steemit would be like the second type above, and act as a way to share content that is off steemit.com. The content could be on any website, even a website powered by steem, or a website powered by a different blockchain. ## How would a user submit a link? Instead of "Submit a Story", you would "Submit a Link". When submitting a Link, it would be similar to submitting a story, except the post of the body would be replaced by a field for you to enter the link. The remaining fields (tags, title, maybe payout options) would remain the same. Any link could be submitted by this method, but one of the cool things about how this could be implemented is that any content created on steem (as a post) could automatically act a link as well. Before diving into that concept, we need to understand what makes a "link" on the blockchain. ## How would it work (technically)? Right now, links could be implemented as a content type simply by creating a comment and specifying a link within the json_metadata. ``` json_metadata: { origin: 'https://blog.steemit.com/steem/@steemitblog/proposed-upgrade-for-blockchain-incentives' } ``` Links could be a `comment` in the blockchain, just one where a `body` field isn't required. They are tagged and indexed, mixed in and ranked right alongside all other content. They just act a bit differently, and may even have different reward structures (as the steemitblog article discussed). ## What would the experience on steemit.com be like? How would this change steemit? This is where the steemitblog/reprint example site comes into play. Imagine if that steemitblog post was submitted with the `json_metadata` shown above (perhaps automatically through a custom CMS). Here's a series of screenshots showing how the UX would work for that post. ### Stumbling upon the post in a feed... ![img](http://i.imgur.com/dLWJ74G.png) --- ![img](http://i.imgur.com/1PxVDw5.png) ### Found on blog.steemit.com ([demo](http://steem.reprint.io/steem/@steemitblog/proposed-upgrade-for-blockchain-incentives)) ![img](http://i.imgur.com/3RwZcMT.png) ### Back on steemit.com... ![img](http://i.imgur.com/fhC4vB5.png) ### Direct links to comments, might make for better community building... ![img](http://i.imgur.com/3FAaQyJ.png) ### Example of a "stub" page... ![img](http://i.imgur.com/OksHsSr.png) --- These aren't incredibly confusing or difficult changes (I don't think), and would offer users a new way to share content outside of the blockchain, while still creating a reference to them on-chain. There are some technical considerations yet to make about rewards, posting limits, uniqueness requirements, and UX - but I think the idea has an incredible amount of potential. ## Automatically linking Steem content Earlier I mentioned that the `body` field of a post wasn't required, but that also doesn't mean it has to be empty. I also mentioned that content submitted to steem (the blockchain) could automatically become a link. To end this entire train of thought off, here's how that could all work. Let's say I create this post (the one you're reading), and on this post, I add the `json_metadata` that a `link` type comment would have (the `origin` parameter). The link I use is to my blog, jesta.us, and is specifically to this article (like [this example](http://jesta.us/steem/@jesta/some-ux-thinking-around-links-as-content-types). The attaching of this json data would happen automatically through a CMS on my Reprint blog running on jesta.us, or any other authoring tool, as to not make it difficult. What I've created now on the blockchain is the hybrid of a comment and a link. On my website, I now have a post displaying like any other post. But on steemit.com, it now is automatically displayed as a link, which people can upvote, comment on or click on to visit my website. This one blockchain entry, as read by two different website engines, acting completely different based on the site it's presented on. ## Closing up Just to wrap this up, I believe content types could offer huge opportunities for development around steem. Not steemit.com, but steem, the blockchain. Steem itself has an incredible potential to become a shared foundation, for an unlimited number of websites, all interconnected by people in a way we've never seen before in history. I see a lot of talk about the economics of the platform, and regardless of how heated that side of this experiment gets, just remember how revolutionary it is over here on the web side of things :)
post[json_metadata]
[tags]
[0] steem
[1] steemit
[2] content-types
[3] links
[4] brainstorming
[image]
[0] http://i.imgur.com/dLWJ74G.png
[1] http://i.imgur.com/1PxVDw5.png
[2] http://i.imgur.com/3RwZcMT.png
[3] http://i.imgur.com/fhC4vB5.png
[4] http://i.imgur.com/3FAaQyJ.png
[5] http://i.imgur.com/OksHsSr.png
[links]
[0] https://steemit.com/steem/@steemitblog/proposed-upgrade-for-blockchain-incentives
[1] http://steem.reprint.io
[2] http://steem.reprint.io/steem/@steemitblog/proposed-upgrade-for-blockchain-incentives
[3] http://jesta.us/steem/@jesta/some-ux-thinking-around-links-as-content-types
[app] steemit/0.1
[format] markdown
post[last_update] 2016-11-20T03:45:33
post[created] 2016-11-20T03:43:06
post[active] 2016-11-30T22:38:36
post[last_payout] 2016-12-21T07:57:09
post[depth] 0
post[children] 17
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] 61.071 SBD
post[curator_payout_value] 2.252 SBD
post[author_rewards] 571404
post[net_votes] 576
post[root_comment] 1394806
post[max_accepted_payout] 1000000.000 SBD
post[percent_steem_dollars] 10000
post[allow_replies] 1
post[allow_votes] 1
post[allow_curation_rewards] 1
post[beneficiaries]
post[url] /steem/@jesta/some-ux-thinking-around-links-as-content-types
post[root_title] Some UX/thinking around Links as content types
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>There's one specific quote I really want to dive into from <a href="https://steemit.com/steem/@steemitblog/proposed-upgrade-for-blockchain-incentives">steemitblog's latest post, "Proposed Upgrade for Blockchain Incentives"</a>.</p> <p>Specifically this line, towards the bottom under "Different Curation Rewards for Different Content Types":</p> <blockquote> <p><strong>Links should not have extremely high author rewards because they are almost entirely requests for curation</strong>.</p> </blockquote> <p>Links as a content type (like posts) - it's something I've been thinking about for a while now, but don't see much chatter about. So I figured I'd write a little bit and potentially stir up some excitement for what this could be.</p> <h2>Preface</h2> <p>Throughout this post I am going to be using a mockup I did for a steemit blog (using reprint), which can be found here: </p> <p>http://steem.reprint.io</p> <p>I will be referring to this site as "blog.steemit.com" in screenshots and code samples, as that's what this site could potentially be someday.</p> <p>I also may be biased towards the awesomeness of this idea simply because I am building reprint, and am willing to admit it :)</p> <h2>What would a content type of "Link" be?</h2> <p>Think about how reddit uses in links to external content on other websites, as content on reddit itself. That's the one line pitch for this new type of content.</p> <p>Reddit has two forms of user generated content: links and selfposts (what a terrible name). They are pretty similar in terms of data, with the one major difference. As you browse reddit, clicking the title of a piece of content does one of two things:</p> <ul><li>You're taken to a reddit page, with a post someone wrote in a subreddit, it's comments, and other related information.</li> <li>You're taken off reddit to an external website.</li> </ul><p>Posts here on steemit are what we have now and are just like the first type above. The "link" content type that could be added to steem/steemit would be like the second type above, and act as a way to share content that is off steemit.com. The content could be on any website, even a website powered by steem, or a website powered by a different blockchain.</p> <h2>How would a user submit a link?</h2> <p>Instead of "Submit a Story", you would "Submit a Link". When submitting a Link, it would be similar to submitting a story, except the post of the body would be replaced by a field for you to enter the link. The remaining fields (tags, title, maybe payout options) would remain the same.</p> <p>Any link could be submitted by this method, but one of the cool things about how this could be implemented is that any content created on steem (as a post) could automatically act a link as well. Before diving into that concept, we need to understand what makes a "link" on the blockchain.</p> <h2>How would it work (technically)?</h2> <p>Right now, links could be implemented as a content type simply by creating a comment and specifying a link within the json_metadata.</p> <p><code>json_metadata: { origin: 'https://blog.steemit.com/steem/@steemitblog/proposed-upgrade-for-blockchain-incentives' }</code></p> <p>Links could be a <code>comment</code> in the blockchain, just one where a <code>body</code> field isn't required. They are tagged and indexed, mixed in and ranked right alongside all other content. They just act a bit differently, and may even have different reward structures (as the steemitblog article discussed).</p> <h2>What would the experience on steemit.com be like?</h2> <p>How would this change steemit? This is where the steemitblog/reprint example site comes into play. Imagine if that steemitblog post was submitted with the <code>json_metadata</code> shown above (perhaps automatically through a custom CMS). </p> <p>Here's a series of screenshots showing how the UX would work for that post.</p> <h3>Stumbling upon the post in a feed...</h3> <p><img src="http://i.imgur.com/dLWJ74G.png" alt="img" /></p> <hr /><p><img src="http://i.imgur.com/1PxVDw5.png" alt="img" /></p> <h3>Found on blog.steemit.com (<a href="http://steem.reprint.io/steem/@steemitblog/proposed-upgrade-for-blockchain-incentives">demo</a>)</h3> <p><img src="http://i.imgur.com/3RwZcMT.png" alt="img" /></p> <h3>Back on steemit.com...</h3> <p><img src="http://i.imgur.com/fhC4vB5.png" alt="img" /></p> <h3>Direct links to comments, might make for better community building...</h3> <p><img src="http://i.imgur.com/3FAaQyJ.png" alt="img" /></p> <h3>Example of a "stub" page...</h3> <p><img src="http://i.imgur.com/OksHsSr.png" alt="img" /></p> <hr /><p>These aren't incredibly confusing or difficult changes (I don't think), and would offer users a new way to share content outside of the blockchain, while still creating a reference to them on-chain. </p> <p>There are some technical considerations yet to make about rewards, posting limits, uniqueness requirements, and UX - but I think the idea has an incredible amount of potential.</p> <h2>Automatically linking Steem content</h2> <p>Earlier I mentioned that the <code>body</code> field of a post wasn't required, but that also doesn't mean it has to be empty. I also mentioned that content submitted to steem (the blockchain) could automatically become a link. To end this entire train of thought off, here's how that could all work.</p> <p>Let's say I create this post (the one you're reading), and on this post, I add the <code>json_metadata</code> that a <code>link</code> type comment would have (the <code>origin</code> parameter). The link I use is to my blog, jesta.us, and is specifically to this article (like <a href="http://jesta.us/steem/@jesta/some-ux-thinking-around-links-as-content-types">this example</a>. The attaching of this json data would happen automatically through a CMS on my Reprint blog running on jesta.us, or any other authoring tool, as to not make it difficult.</p> <p>What I've created now on the blockchain is the hybrid of a comment and a link.</p> <p>On my website, I now have a post displaying like any other post. But on steemit.com, it now is automatically displayed as a link, which people can upvote, comment on or click on to visit my website. This one blockchain entry, as read by two different website engines, acting completely different based on the site it's presented on. </p> <h2>Closing up</h2> <p>Just to wrap this up, I believe content types could offer huge opportunities for development around steem. Not steemit.com, but steem, the blockchain. Steem itself has an incredible potential to become a shared foundation, for an unlimited number of websites, all interconnected by people in a way we've never seen before in history.</p> <p>I see a lot of talk about the economics of the platform, and regardless of how heated that side of this experiment gets, just remember how revolutionary it is over here on the web side of things :)</p>
post[html_preview] <p>There's one specific quote I really want to dive into from steemitblog's latest post, "Proposed Upgrade for Blockchain Incentives".</p><p>Specifically this line, towards the bottom under "Different Curation Rewards for Different Content Types":</p>
post[image] http://i.imgur.com/dLWJ74G.png
post[ts] 1479634986
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