Today, we are going to tackle our third relationship. This relationship takes the author of a piece of content and looks for the highest percentage upvote in the past seven days and given a tie, the most

Last time, we explored the MVC architecture utilized in the Rails framework and were able to finally take some data from the Steem blockchain, transform and filter it in some way, and then serve that

Last time we moved our functions into a Relationship class and we're ready to begin testing out Rails for the first time. However, in order to serve up a web page, we need to write up a simple controller

Last time, we adjusted some code to make things easier to read and nicer to look at. Now we are going to move the code into our Rails project and make the first real commit to the project. By doing this

So now that we have our first relationship, that means we'll never touch it again, right? Nope. In fact, we are going to mess with that code yet again to further improve the style of code to make more

So, last time we finished off our first relationship. We are now able to grab the permlink of the most recent piece of content voted upon by a single account. But as mentioned last time, the implementation

Last time we were able to separate the votes of the author from the rest of the operations in the program that I wrote. However, the relationship we are trying to build requires a single piece of content

Last time, we designed a quick and dirty program that retrieved the most recent operation performed on a specific account. This program used the Radiator gem which allows us to query the Steem blockchain

The overarching goal of Project Greenshift is to provide users with a different and perhaps more useful way to discover new content creators on the Steem blockchain. The plan is to use different relationships

In terms of Project Greenshift, we are still very early in the development of the project. We have yet to write a single piece of code and are still in the early stages of conceptual development. Sure

So, nothing really all that interesting to write about today. Basically setting up my environment to actually begin testing and building things in the future. I decided to upgrade and revamp my development

So, we have developed over the past five blog posts, a basic overview of how the first stage of the project is supposed to work. We have lots of content and want to focus in on a few pieces of content.

So now that we have a starting point, all we need are five different relationships to explore and then we can begin fleshing things out in actual code and testing these ideas on the actual blockchain.

So yesterday I talked about some different relationships that could possibly be explored in Project Greenshift. These relationships are localized meaning that they are derived from the current piece of

So for Project Greenshift, we talked last time about introducing non-linear ways of exploring content that are controlled and influenced by the individual user rather than a strict algorithm. We achieved

So, yesterday we left off establishing the Steemit blockchain as a set of many possible graphs and each piece of content being a node within each of these graphs. Each individual graph serving a some sort

Just jugging with some ideas to toss around. Nothing formal or necessarily well-developed. Just in the early stages of trying to wrap my head around a new idea. The creative engine isn't quite there and

This post serves to mark the conclusion of the q-filter experiment and to give a heads up that the voting bot and vote lottery are now down. I appreciate everyone who has contributed to the project through

Here's another monthly report to discuss the progress that has been made on Q-Filter over the past month. This update also gives some details on some of the problems experienced in during the past two

In order to improve visibility in the future, categories have been implemented to showcase only a subset of different posts according to their primary tag. One can view a category using the following URL