-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Communities Implementation MVP #7
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nities/database.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements communities similarly to as described in the Steem 2017 Roadmap https://steem.com/2017roadmap.pdf.
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 usingcmmts_grant_role
with role receiver [receiver], role [role], and in community id [community]. They can also remove the role by usingcmmts_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_
) 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_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.