Hivewatchers Roadmap

in #hivewatchers15 days ago (edited)


  1. Funding model feasibility review to replace the antiquated on-chain voting model

  2. Scope and guidelines documentation

  3. DHF proposal or similar (depending on outcome of 1)


Funding models

It's a difficult question as to how a project the size of Hivewatchers should be funded. The unfortunate reality is that both members of Hivewatchers must put in at least 20 hours a week for the project to operate. That includes processing reports, liaising with the community, answering chat, conducting investigations, management duties, helping people, and everything else that goes into it. While many hours get donated, not all can be.

So far we've done a review of how the original funding model was established, much of it being before both of our time, and what were the original ideas behind it. A lot of relevant discussion was unfortunately lost when Steemit Inc closed off their Slack to all users that were also on Hive. We're retracing our footsteps as a project in this regard and evaluating what had transpired and what we can learn going forward.

We are also examining the feasibility of various funding models. One is obviously the DHF. Another one is a blended approach as curation of ourselves is largely outside of our control. There will be a post regarding this in the future where we discuss it in detail upon completion of the project.

Scope documentation

The new documentation for Hivewatchers must be written as we're on a new blockchain now and how the community in general has evolved. What will happen in the near future is that these will be drafted and presented on Github. You will see a post announcing this.

One reason for keeping the first draft off chain is to allow for unbiased feedback. Everyone, including users who are blacklisted, are welcome to provide their feedback in Github. We've openly welcomed feedback for a long time now.

Another reason is to allow for easy to track editing and changes, especially minor changes. It would also eventually allow us to build up a set of translations and informational repositories that can be clearly presented. Of course we'll adequately document on chain as well once we have something that's coherent and acceptable.

DHF proposal or similar

There isn't much to say here at this point as step 1 and 2 must be complete before we can go to step 3.

Feedback in General

In regards to feedback in general: We treat all users equally and we don't aim for the most vocal and "influential" users to overshadow the voices of those who are lesser known. Just because someone who is widely supported presented a position, it does not mean that their opinion will be held in higher regard than someone who is new but has excellent ideas for a gap they identified.

Everyone should always provide feedback. We've asked for it before but unfortunately the last time no one provided it. We want feedback that's honest, critical and actionable.

That being said, we are not going to act on changes that benefit a small group or one or two dapps. We are here for the entire Hive ecosystem. That means everyone.

Images by thepeakstudio.

Note: Please report all abuse through the web form.


It's good to see that you are at least working on improving on what you do. Despite what some people may think Hive is being abused in various ways and we need a broad range of community support to combat that.

I think it's vital that we have resources we can point people to show exactly what behaviours might attract downvotes. If they feel they have a case to appeal then there needs to be a responsive team to deal with that. I am sure there are people who would accept some small payment for such work.

BTW This page on your site still refers to Steemit.

Good luck.

You guys really seem overstretch and that seems to be impacting the investigation, so resourcing is a big issue but you know that already.

I see lots of newbies, many genuinely don't know about sourcing or where the line is and keep on making mistakes. Others, of course are just pushing their luck. Would it help to give first time offenders a list of "things frowned upon on Hive" instead of blacklisting them immediately? That may help to keep genuine users on Hive.

In many cases we are unable to tell who is new and who is a fake account, particularly when the user shows clear signs of understanding the community beyond the usual range of a newbie who looked things up.

What would be good to see is more groups aimed at talking to newbies. Right now we refer to The Terminal but I know they can't take on everyone.

I hope Hivewatcher's proposal get enough support to receive funding from DAO because it would be sophisticated method to operate with more ease.

Some people might disagree with it but no system is perfect(not everything can be coded) and we always need some authority who can put some things into check.

Thanks. After seeing your work recently I know your feedback is from a perspective of experience.

I hipe you follows get the funding and automation you need. Youbwork hard and are often victims of abuse because of the fine work you accomplish.

Thank you for the recognition.

Congratulations @hivewatcher! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s) :

You made more than 6500 comments. Your next target is to reach 7000 comments.

You can view your badges on your board And compare to others on the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Do not miss the last post from @hivebuzz:

The Hive community is in mourning. Farewell @lizziesworld!
Support the HiveBuzz project. Vote for our proposal!