#greenshift

So, I've missed the last couple of days due to being stuck at work for consecutive twelve hour days, but given that I'm relatively free I thought I would share an idea I came up with while in the shower

So what's cooler than viewing content rendered outside Steemit? Finishing up our application in just a few lines of code. Of course that statement comes with a huge disclaimer. We're nowhere near having

Last time, we were able to view text that was stored in the blockchain and view it as a raw text String. But the blockchain stores this material in Markdown which can then be further translated into HTML.

Alright. Let's stop screwing around and get some content to show up on the web application. Last time, we fixed things on the model and database end of our data. Now we're going to expand our user interface

So last time, I lost my soul somewhere in a database deep in development hell. This time, hopefully we will have a working application. So, the goal for today is to rebuild our view. Once we get there,

So last time we had a plan? Cool. Today we're going to mess around with some databases and get some results. But first, we need a way to view our database. I mean I'm not sure about you, but I'm not very

Now that we are moving to using an intermediate database to help facilitate data flow and reduce dependence on the blockchain, it would be good to explore how exactly such a database would work. Last time,

So last time, I discussed some different possible directions that we could move into with regards to interacting with blockchain data and integrating traversal and web design on top of it. Using the blockchain

So after programming for a couple of hours, I have nothing really left to show for it. I performed some exploratory solutions to different problems and wasn't really feeling any of them. So, now I left

First off, I like to thank everyone for their feedback in the previous post. It means a lot to hear your comments and criticism and hopefully we can use it to help build Project Greenshift in the future.

So, we haven't done a brainstorming post in a long while so I thought I would open up the floor to some discussion about potential directions this project could take and different goals that I want to

Yesterday we made huge progress through the creation of Post objects which we used to transport data collected from the blockchain to the end user. We were able to display titles to the root webpage. Today,

Now that we have spent the time reorganizing some code and fixing the issues that we've come across, it's time to move forward. So far, we have been able to grab permlinks and pass those to the user interface.

Today, I'm dedicating this entire post to refactoring. Rather than continue to add stuff or fix stuff, we are simply going to clean up some of the messes that I have made over the past few weeks. We'll

This time I wanted to prevent relationships from grabbing comments once and for all. And hopefully I have gotten that fixed. Here's how I went about fixing the relationships that still suffered from this

So before my week-long trip, we left off in kind of a bad spot. The final relationship was not working correctly even though the initial implementation was fleshed out and bugs from edge cases were popping

So, this post is going to be shorter today. I wanted to get the fifth relationship finished, but due to time constraints imposed by my upcoming flight for work, I wasn't able to quite get where I wanted.

At this point in the project, four relationships are functional and there is one left to go. We have saved the most complex and difficult relationship for last. For this relationship, we need to retrieve

So last time, we started working on building our fourth relationship and ran into an obstacle in how resteems are stored on the blockchain. Resteems are treated as custom JSON operations rather than their

Today, we begin tackling our fourth relationship. For this relationship, we want to get the most recently resteemed author's most recent post. The relationship is a little more robust than simply getting