Intro
DIYHub is like a teenage kid to me. It has grown and I even lost track for a short time, but in the past few weeks I have been taking care of it and pushing the project in the direction I want it to go. I know this sounds like a protective and abusive parent, and to be honest, I sometimes feel that way myself.
But I know what's best for you, kid!
I want to make @DIYHub more successful, create a higher impact for creatives on the blockchain, and make it easier for our curators to discover content and interact with our curation bot. At the same time, it is an important goal for us to get our DIYHub community more active within the next 2 months. My personal goal is to crack the 1500 (maybe 2000) subscriber count for the community by the end of this year. If you want to help me achieve this goal, then simply follow this link and give us a follow: https://peakd.com/c/hive-189641/created
Besides the general care of the community and discord, I have changed a lot of things in the background related to our discord bot, added a new helper bot and worked on our planned upcoming web frontend.
Recent Changes
!DIY comment command
Token holders now have the option to send someone DIY Tokens by commenting. As you all know from !beer or !pizza just add !diy into a comment and the parent author will receive 1 token in their wallet.
will turn into:
This only works if you have at least 1 DIY yourself. The more DIY you have, the more you can do this daily. This will hopefully spread the token and, with it, the community and @diyhub account. We just started using it ourselves, and the more we spread it, the more other people will use this command as well. Hopefully.
discord notifications for curators
We have two discord bots in our discord server. One for handling curations and various other commands and one which is proactively forwarding posts into our discord fulfilling various conditions. One of the conditions (and the one we focus the most on) is that a new post gets posted or cross-posted into the DIYHub community. This way, we can spot them more quickly and even receive a notification while we are not actively browsing hive. That helps a lot with following our community focus more and more from everywhere.
handle community posts different from regular curations
Just recently, we changed an important part of our voting bot which executes the manual curations in the background. This bot now distinguishes between community posts and non-community posts. Authors who upload their content into our community (or cross-posts it) will receive a higher upvote and a different appreciation comment. I think that will help us to get higher engagement inside of our own community and hopefully we will be the 1st pick community for them in future posts.
scouted an artist to create a new logo
A really big step in the upcoming weeks is to execute a major rebranding of our content and logo. I decided that we should go with the pastel color scheme and that we should have a self-painted logo by one of our hivers. I asked our curators if they knew of a good artist who is experienced in watercolor painting because we want to re-brand to a more pastel color scheme. @stevenson7 recommended @armandosodano who creates amazing watercolor paintings! (You really should check this guy out!) I am happy that he accepted to work with us on the logo part of our big rebranding and I am super excited with what he will come up ;) Following the new logo, we will decide on the final colors and create assets like a post banner, separators for posts, and all that.
web front end for @diyhub.wiki
In the past week I did a few things, but not enough on the new web frontend. Currently it is still only a wizard and there are many bugs additional to the not finished responsiveness of the app but still it is a good foundation to going forward with.
So why another front-end? The goal of this app is to build a library of useful and curated tutorials which are stored on the hive blockchain and will be accepted and categorized by our team. The idea is that a user has a clean and structured way to post tutorials on hive so the viewer of those tutorials will have a consistent reading flow over all tutorials. Every tutorial posted with the app will get a custom_json attached that will show us the origin of this post. And with this origin, we will receive a notification to review the tutorial. More on that review process later, because here are some screenshots first:
The main design elements, like fonts and margins, will all be changed in the future, as this is only to experiment and to demonstrate what we can do. (I am pretty proud of the idea of adding a gradient in the back-I don't know why, but I like it.)
The individual steps to accomplishing what the tutorial is about can be reordered, changed, removed, or appended. There is a bug when you edit, but that's an easy one I guess. On the right you can see the preview of the rendered markdown, which will be posted at the end.
You will have the option to post it in a community and set Diyhub as the beneficiary. More settings will follow here for sure, but that is the basic stuff already done. What is definitely coming is the buring of DIY tokens from the posting page. If you see the little points counter at the bottom, this is supposed to be a measure of the quality of the post. e.g., the more images/links/steps you add, the more points you will earn when we accept the tutorial. Also, the upvote will be higher which you will receive with this tutorial.
As I've mentioned earlier, we are going to review the tutorial, and if it fits our quality standards, we are going to accept it and assign a category to it. This category will not get stored in a centralized database on the server-it will get posted on-chain via a collection just like peakd does it. If we want to use the collections of peakd or if we want to implement it in our own way, I don't know. It all depends on how quickly and resource-saving we can query the content when a user is accessing the explore page. More on that in a future post.
Next to a search function, there will be a category tree where you can explore and check tutorials from every niche. e.g. If your washing machine is broken: Go to diyhub.wiki and search for a hive post related to the solution to this.
Big thanks to @hivesql
All those changes (especially the bot ones) would have been very difficult with beem which I normally use for bots in python. Hivesql came as a big rescue for me and I want to thank @arcange for providing his support even though I was too stupid to login to the server and locked my account once. I will interact more and more with hivesql and perhaps make the queries on the new web frontend in hivesql as well. For that I will have to code a backend service, which will not be that hard and is needed anyway.
If you don't know hivesql, I can recommend you @geekgirl who wrote:
- https://peakd.com/hive-167922/@geekgirl/hivesql-in-python-which-module-to-choose-pypyodbc-pyodbc-or-pymssql
- https://peakd.com/hive-167922/@geekgirl/hivesql-author-rewards-and-curation-rewards and a few more posts dedicated to specific use-cases
and the official documentation, of course: https://docs.hivesql.io/
More work to come
It feels very good to be back at my old hive project and to be working towards a successful community and curation initiative. If you want to support our curation efforts and let us give higher upvotes to the creators we curate, then feel free to delegate some HP to us. We pay out 100% of your curation rewards, so it will not be a minus-business for you. You can also support us by voting on our recurring curation reports from time to time because this is the only income source we have to give our curators some coins for their hard work.
Thank you for reading and your support of @diyhub! If you have any suggestions, questions, or anything else, leave a comment and we can have a chat :)
Peace!
We also have a discord server: https://discord.gg/c7cRwHv
