Relay operators, please review this NIP-11 variant where you can tell Clients how to behave on-demand based on the connected user and connection history.
The goal is to design a payload structure that informs the policies implemented in each relay, for each user, in a way that Clients can bake these filters into their code.
nostr native is nice. Too bad I already configure a ton of limits in grain 😂
Either way, this would be a great addition.
Now you just need to let me know exactly what limits are those so that Amethyst can preemptively avoid them. :)
If you use this, you can even punish Clients that don't follow it by making harder and harder limits. :)
Yes, progressive limits using auth. Very nice. Anyways, I just pushed AUTH support to grain. The limit configurations would be up to the relay operator. There is an example config here:
https://github.com/0ceanSlim/grain/blob/main/app%2Fstatic%2Fexamples%2Fconfig.example.yml
nostr:nprofile1qqsrx4k7vxeev3unrn5ty9qt9w4cxlsgzrqw752mh6fduqjgqs9chhgppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg6waehxw309aex2mrp0yh8x6rfw3nx7unrv5hx7mn99uslkdah I am hoping you can write your rate limits here and Amethyst can dynamically change our rate limits based on your implementation. :)
Yeah I knew for whom you wrote the nip 😅
when i grow up
this is a good idea esp w auth, but also pls clients lookup nip11 limits also? they are accurate, and if not then shame 🍄
