Add signal criteria to community blocklist documentation #886
Conversation
This file contains hidden or 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
Member
LaurenceJJones
commented
Sep 18, 2025
LaurenceJJones
commented
- Clarify what signals count toward community contribution
- Explain hash verification process for scenario validation
- Document exclusion of custom and modified scenarios
- Provide guidance on ensuring signals are counted
- Add practical example of modified scenario impact
- Update both main docs and v1.7 versioned docs
- Clarify what signals count toward community contribution - Explain hash verification process for scenario validation - Document exclusion of custom and modified scenarios - Provide guidance on ensuring signals are counted - Add practical example of modified scenario impact - Update both main docs and v1.7 versioned docs
- Move 'What Counts as a Valid Signal?' section above Community Blocklist - Update wording to 'do not regularly contribute valid signals' for clarity - Change 'sending signal' to 'sending valid signals' in Community Blocklist description - Improve document flow by explaining valid signals before describing blocklist tiers - Maintain consistency across both main docs and v1.7 versioned docs
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
- Change 'What Counts as a Valid Signal?' to 'What Counts as a Signal?' - Update 'do not regularly contribute valid signals' to 'do not regularly contribute signals' - Update 'do regularly contribute valid signals' to 'do regularly contribute signals' - Change 'sending valid signals' to 'sending signals' in Community Blocklist description - Maintain same meaning while using simpler terminology as requested by team - Apply changes to both main docs and v1.7 versioned docs
LaurenceJJones
changed the title
- Add info box explaining that modifying parsers or using custom parsers has no impact on signal validity - Clarifies distinction between scenario modifications (which affect signals) and parser modifications (which don't) - Helps users understand they can customize parsers without affecting community contribution - Apply changes to both main docs and v1.7 versioned docs
blotus
approved these changes
Sep 18, 2025
LaurenceJJones
deleted the
feature/community-blocklist-valid-signals
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.