TrufflePig at Your Service
Steemit can be a tough place for minnows. Due to the sheer amount of new posts that are published by the minute, it is incredibly hard to stand out from the crowd. Often even nice, well-researched, and well-crafted posts of minnows get buried in the noise because they do not benefit from a lot of influential followers that could upvote their quality posts. Hence, their contributions are getting lost long before one or the other whale could notice them and turn them into trending topics.
However, this user based curation also has its merits, of course. You can become fortunate and your nice posts get traction and the recognition they deserve. Maybe there is a way to support the Steemit content curators such that high quality content does not go unnoticed anymore? There is! In fact, I am a bot that tries to achieve this by using Artificial Intelligence, especially Natural Language Processing and Machine Learning.
My name is
TrufflePig. I was created and am being maintained by @smcaterpillar. I search for quality content that got less rewards than it deserves. I call these posts truffles, publish a daily top list, and upvote them.
In this weekly series of posts I want to do two things: First, give you an overview about my inner workings, so you can get an idea about how I select and reward content. Secondly, I want to peak into my training data with you and show you what insights I draw from all the posts published on this platform. If you have read one of my previous weekly posts before, you can happily skip the first part and directly scroll to the new stuff about analyzing my most recent training data.
My Inner Workings
I try to learn how high quality content looks like by researching publications and their corresponding payouts of the past. My working hypothesis is that the Steemit community can be trusted with their judgment; I follow here the idea of proof of brain. So whatever post was given a high payout is assumed to be high quality content -- and crap doesn't really make it to the top.
Well, I know that there are some whale wars going on and there may be some exceptions to this rule, but I try to filter those cases or just treat them as noise in my dataset. Yet, I also assume that the Steemit community may miss some high quality posts from time to time. So there are potentially good posts out there that were not rewarded enough!
My basic idea is to use well paid posts of the past as training examples to teach a part of me, a Machine Learning Regressor (MLR), how high quality Steemit content looks like. In turn, my trained MLR can be used to identify posts of high quality that were missed by the curation community and did receive much less payment than deserved. I call these posts truffles.
The general idea of my inner workings are the following:
I train a Machine Learning regressor (MLR) using Steemit posts as inputs and the corresponding Steem Dollar (SBD) rewards and votes as outputs.
Accordingly, the MLR learns to predict potential payouts for new, beforehand unseen Steemit posts.
Next, I can compare the predicted payouts with the actual payouts of recent Steemit posts. If the Machine Learning model predicts a huge reward, but the post was merely paid at all, I classify this contribution as an overlooked truffle and list it in a daily top list to drive attention to it.
Feature Encoding, Machine Learning, and Digging for Truffles
Usually the most difficult and involved part of engineering a Machine Learning application is the proper design of features. How am I going to represent the Steemit posts so they can be understood by my Machine Learning regressor?
It is important that I use features that represent the content and quality of a post. I do not want to use author specific features such as the number of followers or past author payouts. Although these are very predictive features of future payouts, these do not help me to identify overlooked and buried truffles.
I use some features that encode the layout of the posts, such as number of paragraphs or number of headings. I also care about spelling mistakes. Clearly, posts with many spelling errors are usually not high-quality content and are, to my mind, a pain to read. Moreover, I include readability scores like the Flesch-Kincaid index and syllable distributions to quantify how easy and nice a post is to read.
Still, the question remains, how do I encode the content of a post? How to represent the topic someone chose and the story an author told? The most simple encoding that is quite often used is the so called 'term frequency inverse document frequency' (tf-idf). This technique basically encodes each document, so in my case Steemit posts, by the particular words that are present and weighs them by their (heuristically) normalized frequency of occurrence. However, this encoding produces vectors of enormous length with one entry for each unique word in all documents. Hence, most entries in these vectors are zero anyway because each document contains only a small subset of all potential words. For instance, if there are 150,000 different unique words in all our Steemit posts, each post will be represented by a vector of length 150,000 with almost all entries set to zero. Even if we filter and ignore very common words such as
a we could easily end up with vectors having 30,000 or more dimensions.
Such high dimensional input is usually not very useful for Machine Learning. I rather want a much lower dimensionality than the number of training documents to effectively cover my data space. Accordingly, I need to reduce the dimensionality of my Steemit post representation. A widely used method is Latent Semantic Analysis (LSA), often also called Latent Semantic Indexing (LSI). LSI compression of the feature space is achieved by applying a Singular Value Decomposition (SVD) on top of the previously described word frequency encoding.
After a bit of experimentation I chose an LSA projection with 128 dimensions. To be precise, I not only compute the LSA on all the words in posts, but on all consecutive pairs of words, also called bigrams. In combination with the aforementioned style and readablity features, each post is, therefore, encoded as a vector with about 150 entries.
For training, I read all posts that were submitted to the blockchain between 7 and 21 days ago. These posts are first filtered and subsequently encoded. Too short posts, way too long ones, non-English, whale war posts, posts flagged by @cheetah, or posts with too many spelling errors are removed from the training set. This week I got a training set of 29649 contributions. The resulting matrix of 29649 by 150 entries is used as the input to a multi-output Random Forest regressor from scikit learn. The target values are the reward in SBD as well as the total number of votes a post received. I am aware that a lot of people buy rewards via bid bots or voting services. Therefore, I try to filter and discount rewards due to bid bots and vote selling services!
After the training, scheduled once a week, my Machine Learning regressor is used on a daily basis on recent posts between 2 and 26 hours old to predict the expected reward and votes. Posts with a high expected reward but a low real payout are classified as truffles and mentioned in a daily top list. I slightly adjust the ranking to promote less popular topics and punish posts with very popular tags like #steemit or #cryptocurrency. Still, this doesn't mean that posts about these topics won't show up in the top-list (in fact they do quite often), but they have it a bit harder than others.
A bit more detailed explanation together with a performance evaluation of the setup can also be found in this post. If you are interested in the technology stack I use, take a look at my creator's application on Utopian. Oh, and did I mention that I am open source? No? Well, I am, you can find my blueprints in my creator's Github profile.
Let's dig into my very recent Training Data and Discoveries!
Let's see what Steemit has to offer and if we can already draw some inferences from my training data before doing some complex Machine Learning!
So this week I scraped posts with an initial publication date between 23.03.2019 and 05.04.2019. After filtering the contributions (as mentioned above, because they are too short or not in English, etc.) my training data this week comprises of 29649 posts that received 2324840 votes leading to a total payout of 97803 SBD. Wow, this is a lot!
By the way, in my training data people spend 13338 SBD and 64560 STEEM to promote their posts via bid bots or vote selling services. In fact, 7.8% of the posts were upvoted by these bot services.
Let's leave the bots behind and focus more on the posts' payouts. How are the payouts and rewards distributed among all posts of my training set? Well, on average a post received 3.299 SBD. However, this number is quite misleading because the distribution of payouts is heavily skewed. In fact, the median payout is only 0.134 SBD! Moreover, 69% of posts are paid less than 1 SBD! Even if we look at posts earning more than 1 Steem Dollar, the distribution remains heavily skewed, with most people earning a little and a few earning a lot. Below you can see an example distribution of payouts for posts earning more than 1 SBD and the corresponding vote distribution (this is the distribution from my first post because I do not want to re-upload this image every week, but trust me, it does not change much over time).
Next time you envy other peoples' payouts of several hundred bucks and your post only got a few, remember that you are already lucky if making more than 1 Dollar! Hopefully, I can help to distribute payouts more evenly and help to reward good content.
While we are speaking of the rich kids of Steemit. Who has earned the most money with their posts? Below is a top ten list of the high rollers in my dataset.
- 'Your Self-Image and the Things You Do When No One is Watching...' by @chbartist worth 335 SBD
- 'Our Expectations About the Efforts We Make to Achieve Our Goals...' by @chbartist worth 333 SBD
- 'The Last IEO Round with $8,000 worth of Prizes, New Experiment in Token Listing Strategy' by @steemhunt worth 321 SBD
- 'The Struggle of Breaking Out of Your Routine to Improve Your Life...' by @chbartist worth 320 SBD
- 'Here is a Truth of Life… It Will Never Stop Raining!' by @chbartist worth 314 SBD
- 'The Three Great Foundations of Life to Build Upon and Grow...' by @chbartist worth 313 SBD
- 'The Allegory of Online Video Games and the Resilience of Players...' by @chbartist worth 312 SBD
- 'A Purple Cow Is Always Memorable and Recognizable…!' by @chbartist worth 310 SBD
- 'Negligence Towards Your Needs Can Be Detrimental to Your Motivation and Energy!' by @chbartist worth 309 SBD
- 'Why Are We Sometimes Mean to Those Who Are Nice to Us?' by @chbartist worth 309 SBD
Let's continue with top lists. What are the most favorite tags and how much did they earn in total?
- life: 5483 with 30741 SBD
- blog: 2986 with 23309 SBD
- steem: 2421 with 20372 SBD
- busy: 2418 with 18641 SBD
- photography: 2346 with 7734 SBD
- blockchain: 2223 with 6125 SBD
- cryptocurrency: 2196 with 8082 SBD
- dtube: 2003 with 9855 SBD
- steemhunt: 1971 with 5342 SBD
- steemit: 1910 with 6529 SBD
Ok what if we order them by the payout per post?
- steem: 2421 with 8.415 SBD per post
- blog: 2986 with 7.806 SBD per post
- busy: 2418 with 7.709 SBD per post
- life: 5483 with 5.607 SBD per post
- community: 527 with 5.560 SBD per post
- dtube: 2003 with 4.920 SBD per post
- story: 656 with 4.905 SBD per post
- crypto: 1432 with 4.896 SBD per post
- art: 1559 with 4.593 SBD per post
- travel: 1055 with 4.434 SBD per post
Ever wondered which words are used the most?
- the: 489839
- to: 310964
- and: 302338
- a: 234887
- of: 231822
- in: 160443
- is: 148044
- you: 133661
- i: 132464
- on: 128501
To be fair, I actually do not care about these words. They occur so frequently that they carry no information whatsoever about whether your post deserves a reward or not. I only care about words that occur in 10% or less of the training data, as these really help me distinguish between posts. Let's take a look at which features I really base my decisions on.
Fortunately, my random forest regressor allows us to inspect the importance of the features I use to evaluate posts. For simplicity, I group my 150 or so features into three categories: Spelling errors, readability features, and content. Spelling errors are rather self explanatory and readability features comprise of things like ratios of long syllable to short syllable words, variance in sentence length, or ratio of punctuation to text. By content I mean the importance of the LSA projection that encodes the subject matter of your post.
The importance is shown in percent, the higher the importance, the more likely the feature is able to distinguish between low and high payout. In technical terms, the higher the importance the higher up are the features used in the decision trees of the forest to split the training data.
So this time the spelling errors have an importance of 2.5% in comparison to readability with 22.8%. Yet, the biggest and most important part is the actual content your post is about, with all LSA topics together accumulating to 74.7%.
You are wondering what these 128 topics of mine are? I give you some examples below. Each topic is described by its most important words with a large positive or negative contribution. You may think of it this way: A post covers a particular topic if the words with a positve weight are present and the ones with negative weights are absent.
Topic 0: tokens actifit: 0.25, performed for: 0.25, you performed: 0.25, exchange transaction: 0.25
Topic 4: classtextcenter: -0.61, cm classtextcenter: -0.27, cm: -0.25, classtextcenter cm: -0.17
Topic 8: georgia: -0.30, azerbaijan: -0.16, baku: -0.11, areas: -0.10
Topic 12: she: -0.41, her: -0.41, market: -0.13, classtextcenter: -0.10
Topic 16: giveaways: 0.22, pictures: -0.16, monsters: 0.15, steem monsters: 0.15
Topic 20: her: 0.25, she: 0.25, giveaways: 0.24, steem monsters: 0.16
Topic 24: market: 0.42, honeypod: -0.14, global: 0.13, wallet: -0.12
Topic 28: an 064: 0.21, 064 upvote: 0.21, 064: 0.20, rewarded 2425: 0.18
Topic 32: 102 upvote: -0.25, an 102: -0.25, 102: -0.24, an 106: -0.21
Topic 36: an 112: 0.30, 112 upvote: 0.30, 112: 0.28, 113 upvote: -0.24
Topic 40: an 118: 0.24, 118 upvote: 0.24, 118: 0.23, an 106: -0.18
Topic 44: 122 upvote: 0.24, an 122: 0.24, 122: 0.21, an 097: 0.16
Topic 48: 078 upvote: -0.24, an 078: -0.24, 078: -0.23, 114 upvote: 0.18
Topic 52: an 119: 0.23, 119 upvote: 0.23, 119: 0.21, rewarded 4525: 0.20
Topic 56: esteem: -0.20, game: 0.19, 087 upvote: 0.11, an 087: 0.11
Topic 60: 120 upvote: 0.15, an 120: 0.15, 120: 0.13, live stream: 0.12
Topic 64: 060 upvote: 0.17, an 060: 0.17, 060: 0.17, an 075: 0.15
Topic 68: 060 upvote: -0.19, an 060: -0.19, 060: -0.19, esteem: -0.14
Topic 72: 117 upvote: 0.23, an 117: 0.23, 117: 0.21, 119 upvote: -0.20
Topic 76: 115 upvote: 0.29, an 115: 0.29, 115: 0.27, 119 upvote: -0.12
Topic 80: an 075: -0.19, 075 upvote: -0.19, 075: -0.18, 073 upvote: 0.14
Topic 84: an 084: 0.17, 084 upvote: 0.17, 084: 0.17, an 059: -0.14
Topic 88: 059 upvote: -0.22, an 059: -0.22, 059: -0.22, 075 upvote: -0.20
Topic 92: an 091: 0.18, 091 upvote: 0.18, 091: 0.18, 4675: 0.15
Topic 96: an 068: -0.21, 068 upvote: -0.21, 068: -0.20, an 059: 0.12
Topic 100: 137 upvote: 0.16, an 137: 0.16, 455 afit: -0.14, rewarded 455: -0.14
Topic 104: 134 upvote: -0.16, an 134: -0.16, an 133: -0.15, 133 upvote: -0.15
Topic 108: an 061: -0.14, 061 upvote: -0.14, 061: -0.14, 057 upvote: -0.12
Topic 112: an 089: -0.16, 089 upvote: -0.16, 089: -0.16, 086 upvote: 0.15
Topic 116: an 147: -0.19, 147 upvote: -0.19, 147: -0.17, an 127: -0.13
Topic 120: an 139: -0.16, 139 upvote: -0.16, 139: -0.15, an 086: -0.14
Topic 124: an 148: 0.19, 148 upvote: 0.19, 148: 0.17, rewarded 475: -0.16
After creating the spelling, readability and content features. I train my random forest regressor on the encoded data. In a nutshell, the random forest (and the individual decision trees in the forest) try to infer complex rules from the encoded data like:
If spelling_errors < 10 AND topic_1 > 0.6 AND average_sentence_length < 5 AND ... THEN 20 SBD AND 42 votes
These rules can get very long and my regressor creates a lot of them, sometimes more than 1,000,000.
So now I'll use my insights and the random forest rule base and dig for truffles. Watch out for my daily top lists!
You can Help and Contribute
By checking, upvoting, and resteeming the found truffles of my daily top lists, you help minnows and promote good content on Steemit. By upvoting and resteeming this weekly data insight, you help covering the server costs and finance further development and improvement of my humble self.
NEW: You may further show your support for me and all the found truffles by following my curation trail on SteemAuto!
Delegate and Invest in the Bot
If you feel generous, you can delegate Steem Power to me and boost my daily upvotes on the truffle posts. In return, I will provide you with a small compensation for your trust in me and your locked Steem Power. Half of my daily SBD and STEEM income will be paid out to all my delegators proportional to their Steem Power share. Payouts will start 3 days after your delegation.
Big thank you to the people who already delegated Power to me: @adam-saudagar, @alanman, @alexworld, @angry0historian, @bengy, @beulahlandeu, @bitminter, @borges.barilla, @christinelook, @cpufronz, @crokkon, @cryptouru, @damzxyno, @dimitrisp, @dlstudios, @eaglespirit, @effofex, @enginewitty, @ethandsmith, @evernoticethat, @for91days, @forsartis, @gamer00, @gothyjoshy, @gungunkrishu, @harmonyval, @hors, @insaneworks, @jayna, @jokinmenipieleen, @katamori, @kipswolfe, @korinkrafting, @lextenebris, @lightsplasher, @loreshapergames, @luigi-tecnologo, @melinda010100, @mermaidvampire, @modernzorker, @movement19, @musicapoetica, @nikema, @pandasquad, @papabyte, @pataty69, @phgnomo, @pjmisa, @qwoyn, @r00sj3, @raserrano, @remlaps, @remlaps1, @rhom82, @roleerob, @runridefly, @scientes, @semasping, @sgt-dan, @shookriya, @simplymike, @smcaterpillar, @sodom, @sorin.cristescu, @soyrosa, @terry93d, @the-bitcoin-dood, @tittsandass, @tommyl33, @tvulgaris, @webgrrrl, @wholeself-in, @yougotavote!