Inspired by nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 idea, #Nostr relay implementation #Nosflare has been updated to v4.22.25 with NIP-05 validation! In order to publish an event, a valid Nostr address must be stored for the pubkey's latest kind 0 event. If none is found on the Nosflare-powered relay itself, it'll fallback to an external relay (nostr.band) to check. There's also option to allow or block specific domains. Test it out now using wss://relay.nosflare.com

https://github.com/Spl0itable/nosflare

note1lphqcapvylxw75xwlwjr6pte27nyv546njf2d05ms75m5qe4q0aqc2zqme

Reply to this note

Please Login to reply.

Discussion

Do you see any speed drop due to this?

I guess you could cache the npub for 30 minutes or so, so you don't need to do the validation all the time. Just check the cache and invalidate every 30 mins.

No speed drop and it caches the validation for 1hr 😎

How’s your CF bill so far? Getting a lot of R2 read/writes/lists?

Recently implented some heavy rate limiting for REQ messages. Including completely dropping those who include blocked kinds.

So far so good. Fortunately, R2 has cheap class B ops after the first 10 mill

@note1pzw4h8076nthzzt7mnyt3esheaykdlcsqz5qpta8eqrujfqvzvksnzl9n9

Makes sense. I am yet to find some time to contribute, we need to get it into a proper structure and use typescript. I also think there are caching optimizations that could be made. As well as, usage for DO and event propagation.

Building out for other serverless would be awesome 🤙

Nice nostr:npub16jdfqgazrkapk0yrqm9rdxlnys7ck39c7zmdzxtxqlmmpxg04r0sd733sv I believe I’m already running nosflare but if not… I am now