Anyone can create a community with cmmts_create with id [id]. A community's ID should never be displayed to the end user and is restricted to only the lowercase alphabet including dashes (-). They will automatically receive the role 'owner'. Then they can assign roles owner, admin, mod, author to other users by using cmmts_grant_role with role receiver [receiver], role [role], and in community id [community]. They can also remove the role by using cmmts_remove_role with the same permissions. If a role is granted to the nonexistent account @eo, then it is considered granted to everyone by the node software. This allows for public communities where anyone can post.
Here are the permissions each role has. Note that each role can remove any other user in the same role or below (except author which can only post).
Anyone with role author or above can post by creating a post with a property json_metadata of the full network prefix (for mainnet this would be stratos_0_) plus cmmts_post (for example in mainnet this would be stratos_0_cmmts_post) containing the id of the community to post to.
Anyone with role mod or above can block (remove) a post by creating a cmmts_block_post operation with permlink [permlink], author [author], and in community id [community].
Anyone with role mod or above can feature a post by creating a cmmts_feature operation with permlink [permlink], author [author], and in community id [community].
That's the basis of transactions, documentation for APIs will follow soon.
This implements communities similarly to as described in the Steem 2017 Roadmap https://steem.com/2017roadmap.pdf.
Anyone can create a community with
cmmts_createwith id [id]. A community's ID should never be displayed to the end user and is restricted to only the lowercase alphabet including dashes (-). They will automatically receive the role 'owner'. Then they can assign roles owner, admin, mod, author to other users by usingcmmts_grant_rolewith role receiver [receiver], role [role], and in community id [community]. They can also remove the role by usingcmmts_remove_rolewith the same permissions. If a role is granted to the nonexistent account @eo, then it is considered granted to everyone by the node software. This allows for public communities where anyone can post.Here are the permissions each role has. Note that each role can remove any other user in the same role or below (except author which can only post).
Anyone with role author or above can post by creating a post with a property json_metadata of the full network prefix (for mainnet this would be
stratos_0_) pluscmmts_post(for example in mainnet this would bestratos_0_cmmts_post) containing the id of the community to post to.Anyone with role mod or above can block (remove) a post by creating a
cmmts_block_postoperation with permlink [permlink], author [author], and in community id [community].Anyone with role mod or above can feature a post by creating a
cmmts_featureoperation with permlink [permlink], author [author], and in community id [community].That's the basis of transactions, documentation for APIs will follow soon.