cameri / nostream / 41530042526

78%

Build Type

push

github

Committed by web-flow

Commit Message

feat(peering): treat authenticated peers as feeds  (#1034)

<!--- Provide a general summary of your changes in the Title above -->

## Description
<!--- Describe your changes in detail -->
This PR :- 
- Adds \`limits.peer\` with separate subscription caps and message rate
limits for authenticated peering peers.
- Peer REQ, COUNT and NIP-77 filter handling use peer caps instead of
client caps; a full-feed subscription no longer trips
\`max_subscriptions\` or the client EWMA message bucket.
- \`limits.peer.subscription.maxLimit\` defaults to 0 (no cap), so a
peer can request a full feed.
- Peer messages are counted in a separate rate-limit bucket; defaults
remain high but finite.
- Only a verified AUTH from an enabled \`peering.peers\` pubkey selects
peer limits. Unauthenticated and unconfigured connections keep the
existing client limits exactly as before.
- Documents and validates the new limits.

## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an
issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps
to reproduce -->
<!--- Please link to the issue here: -->
Closes :- #934
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran
to -->
<!--- see how your change affects other areas of the code, etc. -->

## Screenshots (if appropriate):

## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Non-functional change (docs, style, minor refactor)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to cha... (continued)

Coverage Stats

4531 of 6374 branches covered (71.09%)

Branch coverage included in aggregate %.

57 of 57 new or added lines in 8 files covered. (100.0%)

1 existing line in 1 file now uncovered.

9832 of 12122 relevant lines covered (81.11%)

758.28 hits per line