diff options
| -rw-r--r-- | 11.md | 7 |
1 files changed, 7 insertions, 0 deletions
| @@ -79,6 +79,7 @@ are rejected or fail immediately. | |||
| 79 | "min_pow_difficulty": 30, | 79 | "min_pow_difficulty": 30, |
| 80 | "auth_required": true, | 80 | "auth_required": true, |
| 81 | "payment_required": true, | 81 | "payment_required": true, |
| 82 | "restricted_writes": true, | ||
| 82 | "created_at_lower_limit": 31536000, | 83 | "created_at_lower_limit": 31536000, |
| 83 | "created_at_upper_limit": 3 | 84 | "created_at_upper_limit": 3 |
| 84 | }, | 85 | }, |
| @@ -124,6 +125,12 @@ Even if set to False, authentication may be required for specific actions. | |||
| 124 | 125 | ||
| 125 | - `payment_required`: this relay requires payment before a new connection may perform any action. | 126 | - `payment_required`: this relay requires payment before a new connection may perform any action. |
| 126 | 127 | ||
| 128 | - `restricted_writes`: this relay requires some kind of condition to be fulfilled in order to | ||
| 129 | accept events (not necessarily, but including `payment_required` and `min_pow_difficulty`). | ||
| 130 | This should only be set to `true` when users are expected to know the relay policy before trying | ||
| 131 | to write to it -- like belonging to a special pubkey-based whitelist or writing only events of | ||
| 132 | a specific niche kind or content. Normal anti-spam heuristics, for example, do not qualify. | ||
| 133 | |||
| 127 | - `created_at_lower_limit`: 'created_at' lower limit as defined in [NIP-22](22.md) | 134 | - `created_at_lower_limit`: 'created_at' lower limit as defined in [NIP-22](22.md) |
| 128 | 135 | ||
| 129 | - `created_at_upper_limit`: 'created_at' upper limit as defined in [NIP-22](22.md) | 136 | - `created_at_upper_limit`: 'created_at' upper limit as defined in [NIP-22](22.md) |