I've been pushing hard to make #Nosflare a leading #Nostr relay 😎
Happy to say a lot has been improved in v1.7.6
- Added rate-limiting
- Added support for blocklisting pubkeys and kinds
- Added back support for all kinds unless blocked
- Improved in-memory caching
- Other general optimizations
nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w if you have the time, would appreciate you poking holes at this. Have made a lot of changes! 🙏
Was just looking, and I think that the implementation of rate limiting as is, will not work. The cheapest alternative is Durable Objects (if no DDoS) or Cloudflare native offering that only charges for passed requests. I haven’t looked at anything else yet, but will try later 🐶🐾🫡
Also, don’t forget that workers do not survive beyond single request and their Date.now() is frozen when they execute
I've been holding off on using Durable Objects as it is location bound. Whereas, with KV, it'll eventually have all data stored throughout Cloudflare PoPs.
DO is location bound because they are serialized and they migrate location. Look at CF examples with conceptual implementation of the rate limiters. I’d suggest to remove rate limiters for now and allow CF do the protection, or you’ll end up paying more for rate limiting than if you would have allowed the request to pass 🐶🐾🫡
