scrobble.life
#vyb

VYB Curation Project (VCP): February '22 Update & Discussion

@vyb.vyb@vyb.vyb (59)1674d

Feedback has been received for various areas of the project and some changes are to follow. As stated in the announcement post, we're in a trial phase until April 22nd 2022 to allow for flexibility and adjustments to the curation model and the project overall.


[1]



Distribution/Curation Data Post

The current format for the data post has multiple issues which restrict comprehension of the curators efforts.

Problem

  1. Post & comment votes are combined
  2. Total vote weight used for each curator is provided (below the tables) but the vote weight used towards each individual author is not
  3. The beneficiary attached to the data post isn't a reliable way to reward the efforts for those collating the data (previously set at 80%)

Solution

  1. Comment votes will be dropped from the outgoing vote totals as the curation trail does not follow behind comment votes Comment and post votes can't be separated using HIVE SQL, so we're going to include comment voting with the trail and link this change with point 2 below
  2. The rank column will be dropped from tables and the total vote weight used per author will be added instead. This will be in descending order, so the account with the highest total vote weight received will be at the top of the table
  3. The beneficiary will change to 100% and an upvote using vyb.pob (and possibly vyb.fund) account will be applied to the data post to provide the data collator with a consistent reward (while also removing the ability for @vyb.curation to receive upvote rewards from these accounts)


[2]

Communication & Curator Opportunity

Heavy reliance on third-party applications like Discord, Telegram, Slack, etc. for communication with curators is an issue when we're looking to boost engagement and decentralisation on the platform.

Problem

  1. Limited interaction with the overall community which is reducing the opportunities for curation expanding outward
  2. The use of Discord as the main method for interaction with curators is creating an 'echo chamber' while also adding to point 1.
  3. Curator selection is limited due to the sphere of influence held by the VCP Admin(s)

Solution

  1. Communication post to be published on @vyb.hub* (then reblogged by @vyb.vyb) on the day of curator swap-over. This will include details about the curation trail and delegation allocation for the curators during the previous week, as well as a method for people to request curatorship (outside-in) and for previous/current curators to provide feedback (inside-out)
  2. As above.
  3. An application process will be shared within the communication post which will provide an avenue for interested persons to get involved with the curation efforts (specifically @vyb.curation curation blocks to begin with as VYB Check is still largely in development with the initial core group)


[2]

VYB Curation

is the main funnel for the VCP distribution/curation model. Curators are followed by the @vyb.curation account and its voting trail on a weekly basis and the data for outgoing votes are published on the vyb.curation account for the community to review. There are no guidelines set for the curators so they can vote how they like with the understanding that their upvotes will be publicly shared and acknowledged by the community.

Requesting community feedback for below. This isn't to say that problems and solutions aren't identified and being discussed or implemented already.

Problem 1. 2. 3.

Solution

1. 2. 3.


The above points will be updated with feedback received from the comments and credit will be assigned.



[2]

VYB Check

is a method for rewarding excellent content through a submission and approval process. This process is backed with reason and transparency to ensure that some level of accountability is maintained for the curation votes received.

Problem

  1. VYB Check workflow has primarily been off-chain during the initial stages to provide room for improvements and flexibility
  2. Checkers have no incentivisation, except through their own intrinsic motivation, to approve/deny submitted posts by curators
  3. Posts outside of the VYB/POB tags cannot be rewarded by the VYB Check VYB/POB upvotes
  4. No method for VYB Check accountability has been set up like the VCP Distribution Data posts
  5. Limited potential for !vybcheck submissions if restricted to VCP curators only

Solution

  1. All VYB Checks will be moved on-chain with Discord being used to post the initial comment submission for Checkers to respond to (this will move to be fully on-chain once automation is set up for the @vyb.check comment response)
  2. Sponsorships for Checkers are being offered by @proofofbrainio to assist with the VYB Check testing phase during the 3-month trial. This will be in the form of a POB delegation and curation trail follow from the @proofofbrainio account

2.5. A method for rewarding liquid/staked POB/VYB to curators (submissions) and checkers (approvals/denials) is being developed. This will come from the curation rewards earned by the main trail generator (vyb.pob), after the initial 50% of the rewards have been sent to support the development of Proof of Brain via the @pob-fund account. 3. A post called "VYB Check Approval Notifier" has been published to act as a bridge for rewarding these posts. 4. Approvals and denials by the Checkers will be posted on the @vyb.curation account in a data post. 5. We're going to test grounds with the !vybcheck submission process as a platform-wide solution, initially starting with a one-week trial phase.



[2]

*@vyb.hub is being created as an on-chain method of communication for specific areas of the VYB tribe. This will include, but is not limited to: tech-support/issues, moderation, governance, curation, distribution. Further details of this layer of communication will be posted in an announcement post via @vyb.hub.


@vyb.curation trail support

<img src=" ">

CLICK to visit the @vyb.curation curation trail page





[1-2]

Creative Commons Licence

[vyb.vyb](this post)

Comments · 5

  • @aurikan(57)· 1478d

    Me gustaria saber si el proyecto VYB , sigue vivo??? alguien trabajando aqui? tengo interes y me pregunto si hay algun motivo para promediar?? gracias de antemano por su tiempo

  • @calumam(64)· 1672d

    Notification for some testing involving the @vyb.curation curation trail.

    I've been communicating with the curators for the past couple of days trying to gain clarity on the comment voting process while being followed by the trail. It dawned on me that it's probably easier to just follow @calumam at the same setting and I'll make a handful of votes and document them below in replies.

    Scaled voting is working for Post voting below 50%, but not for comment voting. Fixed voting is possibly working for comment votes at 50%+ (the default figure for fixed voting), although the votes from the accounts following behind on the trail are still scaled (see image below).

    image.png

    @samsmith1971 made a 51.3% upvote on this comment and vyb.curation followed behind with the 50% scaled upvote (25.7%) and a handful of the trail followers followed that upvote with their allocated percentages.

    So, the vote at or above 50% triggered the fixed vote weight threshold for the comment vote, and the scaled vote weight setting still applied to the trail supporters.

    Testing:

    I'll make a 49% upvote on a comment while being followed by the trail with the 'Vote comments too' box enabled.

    link

    I'll make a 51% upvote on a comment while being followed by the trail with the 'Vote comments too' box enabled.

    link


    Update: The 49% upvote worked so I'll try some lower percentages.

    I'll make a 20% upvote on a comment while being followed by the trail with the 'Vote comments too' box enabled.

    link

    I'll make a 30% upvote on a comment while being followed by the trail with the 'Vote comments too' box enabled.

    link

    I'll make a 40% upvote on a comment while being followed by the trail with the 'Vote comments too' box enabled.

    link

    Update 2:

    40% upvotes to comments are working but with limited trail support. This, and the 49% upvote, negates the theory of the fixed vote weight threshold being the issue. For the time being, I will notify the Aware Curators of this comment thread and the working upvotes so that comment voting can be utilised to distribute via the trail and discrepancies in the data post can be avoided.

    As mentioned above in the main post, a "Curator Changeover" post will be published from the @vyb.hub account on Sunday and within this, there will be information about comment voting via the @vyb.curation trail. We'll also be looking for solutions to the Post & Comment data separation using HIVE SQL so other options can be explored.

    Curation trail from @vyb.curation to @calumam has been unfollowed.


    Why this is important?

    If comment upvotes below the 50% threshold aren't being followed by the trail, when the curators outgoing vote data is published there will be discrepancies for all of these sub-50% upvotes assigned to comments (no trail support = inaccurate figures for distribution of tokens). This being said, the intention is still evident from the figures and all curators were made aware of comment voting being enabled prior to their curator block.

    Huge thank you to @samsmith1971 for the assistance and feedback during this change. Considerations will be added to the data post WC 02/28/22 to provide clarity for the potential discrepancies during the previous week.

  • @thomashnblum(69)· 1673d

    I believe the idea of ​​posting curated updates via @vyb.hub will be of great help in maintaining a more accessible flow of information than discord. I really have a hard time keeping up to date on discord and reading all the chats that end up being filled with news and this causes me a feeling of absence and maybe a false impression that I don't "care". The fact is that I have little free time to dedicate to the project other than the work itself of carefully curating it. I don't mind that I'm not necessarily able to follow the conversation if that's not essential, but I think that if the VYB curator's plan is to have a strong and fully connected team, it makes more sense to transfer my role to someone who can integrate more and be active on the team. In no way would this make me sad, I'm grateful for the experience I've had so far and I will continue to participate in Vyb anyway, since I joined Hive my vision is of "curation".

  • @notconvinced(62)· 1674d

    I'm glad you guys are seeing issues, addressing them and evolving.

    Problem

    1. Voting high hp staked individuals for higher hive returns.
    2. Few high vyb stakes centralizing vote power, just like on hive.

    Solution 1&2. Try to curate smaller fish who don't normally get as much notice and maybe give advice, so they can improve.

  • @themarkymark(81)· 1674d

    Comment and post votes can't be separated using HIVE SQL

    Why is this? This should be possible.