Curation Model

A temporary one page explainer for curators
This is meant as a placeholder description for the benefit of the content curation working group before a full article can be prepared.
The curator model is centered around workers, and the lead, in the curator working group. These actors can engage in a range of special activities in the content directory which others canno

Frozen Features

  • Update permissions of a curator group.
  • Update channel privilege level.
  • Update channel NFT limit.
  • Update paused features of a channel.
Certain features are currently implemented, but frozen - hence not accessible on the runtime, due limit scope of testing required for mainnet.

Moderation Actions

These actions, referred to as curation, are currently
pub enum ContentModerationAction {
// Related extrinsics:
// - `set_video_visibility_as_moderator`
// Related extrinsics:
// - `set_channel_visibility_as_moderator`
// Related extrinsics:
// - `set_channel_paused_features_as_moderator` - each change of `PausableChannelFeature` `x` requires permissions
// for executing `ChangeChannelFeatureStatus(x)` action
// Related extrinsics:
// - `delete_video_as_moderator`
// Related extrinsics:
// - `delete_channel_as_moderator`
// DeleteVideoAssets(is_video_nft_status_set)
// Related extrinsics:
// - `delete_video_assets_as_moderator` - deletion of assets belonging to a video which has an NFT issued
// requires permissions for `DeleteVideoAssets(true)` action, deleting other video assets requires permissions for
// `DeleteVideoAssets(false)`.
// Related extrinsics:
// - `delete_channel_assets_as_moderator`
// Related extrinsics:
// - `update_channel_nft_limit`
Notice a few things
  • hiding is a signal which causes Argus to not distribute this content to end-users, for channels it implies all dataobjects for the channel and any video in the channel, and for a video it implies all data objects for that video.
  • deleting a video is only possible if no NFT has been issued, however, deleting data objects for this video is always possible.
  • deleting a channel is only possible if it has no videos, and it involves delting all data objects for this channel.
  • where PausableChannelFeature encompasses the following channel features which can be paused.
pub enum PausableChannelFeature {
// Affects:
// -`withdraw_from_channel_balance`
// -`claim_and_withdraw_channel_reward`
// Affects:
// - `claim_channel_reward`
// - `claim_and_withdraw_channel_reward`
// Affects:
// - `issue_nft`
// - `create_video` (if `auto_issue_nft` provided)
// - `update_video` (if `auto_issue_nft` provided)
// Affects:
// - `create_video`
// Affects:
// - `update_video`
// Affects:
// - `update_channel`
// Affects:
// - `issue_creator_token`

Curator Groups and Permissions

Since many of these actions are quite invasive, there is a permissioning system which constrains exactly what curator can do what actions on a given channel. To make the management of curators, and their permissions, practical at scale, the concept of curator groups has been introduced. A curator can be part of none or many such groups, and the permissions exist at the group level, not curator. Channels are partitioned into permission levels called channel privelege levels. When first created a channel has a default level, but this can be updated later by the lead. The levels themselves have no direct meaning, and are identified by integers, but there is no relationship between the permissions of a channel and the level. The permissions of a curator group describe what moderation actions group members can do for different levels. If no such action description exists for a given permission level, then group members cannot do any moderation action at all for channels with this level.