AtHeartEngineer/rfc-index
1
0
Fork 0
mirror of https://github.com/vacp2p/rfc-index.git synced 2026-01-06 22:34:02 -05:00
Code Issues Packages Projects Releases Wiki Activity

Fix Linting Errors (#135)

Browse Source 
Fix the current markdown-linting errors.
This commit is contained in:
Jimmy Debe
2025-03-07 10:36:06 -05:00
committed by GitHub
parent 0277fd0c4d
commit f4b34afd1a
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
status/56/communities.md
View File

@@ -310,13 +310,14 @@ Note: The usage of the clock is described in the [Clock](#clock) section.
### Functional scope and shard assignment
We define two special [functional scopes](../raw/status-app-protocols.md#functional-scope) for messages related to Status Communities:
1. Global community control
2. Global community content
All messages that relate to controlling communities MUST be assigned the _global community control_ scope.
All messages that carry user-generated content for communities MUST be assigned the _global community content_ scope.
> *Note:* a previous iteration of Status Communities defined separate community-wide scopes for each community.
> **Note:** a previous iteration of Status Communities defined separate community-wide scopes for each community.
However, this model was deprecated and all communities now operate on a global, shared scope.
This implies that different communities will share shards on the routing layer.
@@ -324,6 +325,7 @@ The following [Waku transport layer](../raw/status-app-protocols.md#waku-transpo
As per [STATUS-SIMPLE-SCALING](https://rfc.vac.dev/status/raw/simple-scaling/#relay-shards), communities use the default cluster ID `16`
set aside for all Status app protocols.
Within this cluster, the following [shards](../raw/status-app-protocols.md#pubsub-topics-and-sharding) are reserved for the community functional scopes:
1. All messages with a _global community control_ scope MUST be published to shard `128`
2. All messages with a _global community content_ scope MUST be published to shard `256`

2
status/raw/status-app-protocols.md
View File

@@ -96,7 +96,7 @@ All Status messages MUST have one of these functional scopes:
1. _Global community control_: messages enabling the basic functioning of the app to control features related to communities. Examples include Community Invites, Community Membership Updates, community Status Updates, etc.
2. _Global community content_: messages carrying user-generated content for members of any community.
> *Note:* a previous iteration of the Status Communities feature defined separate community-wide scopes for each community.
> **Note:** a previous iteration of the Status Communities feature defined separate community-wide scopes for each community.
However, this model was deprecated and all communities now operate on a global, shared scope.
This implies that different communities will share shards on the routing layer.