Remove min_prefix mentions from NIP-11 after prefix search was removed from NIP-01

This commit is contained in:
Viktor Vsk 2023-08-20 14:27:03 +02:00 committed by fiatjaf_
parent c5a8b75abd
commit 89915e0251

5
11.md
View File

@ -75,7 +75,6 @@ are rejected or fail immediately.
"max_filters": 100, "max_filters": 100,
"max_limit": 5000, "max_limit": 5000,
"max_subid_length": 100, "max_subid_length": 100,
"min_prefix": 4,
"max_event_tags": 100, "max_event_tags": 100,
"max_content_length": 8196, "max_content_length": 8196,
"min_pow_difficulty": 30, "min_pow_difficulty": 30,
@ -102,9 +101,6 @@ Must be one or higher.
- `max_subid_length`: maximum length of subscription id as a string. - `max_subid_length`: maximum length of subscription id as a string.
- `min_prefix`: for `authors` and `ids` filters which are to match against
a hex prefix, you must provide at least this many hex digits in the prefix.
- `max_limit`: the relay server will clamp each filter's `limit` value to this number. - `max_limit`: the relay server will clamp each filter's `limit` value to this number.
This means the client won't be able to get more than this number This means the client won't be able to get more than this number
of events from a single subscription filter. This clamping is typically done silently of events from a single subscription filter. This clamping is typically done silently
@ -284,7 +280,6 @@ As of 2 May 2023 the following `curl` command provided these results.
"max_filters":2500, "max_filters":2500,
"max_limit":5000, "max_limit":5000,
"max_subid_length":256, "max_subid_length":256,
"min_prefix":4,
"max_event_tags":2500, "max_event_tags":2500,
"max_content_length":65536, "max_content_length":65536,
"min_pow_difficulty":0, "min_pow_difficulty":0,