Oh boy, I swear I didn’t think it through or even planned for it at all. But seeing some major relays die, I felt that I had to step up at least for our paying customers 🚀🚀🚀
(Pre-release but can be used today)
Login to reply
Replies (32)
Way to step up! Thank you. 🫂
Damn it feels good to be a @npub1nxy4...avr7 customer. 😎
Oh boy, I swear I didn’t think it through or even planned for it at all. But seeing some major relays die, I felt that I had to step up at least for our paying customers 🚀🚀🚀
(Pre-release but can be used today)
View quoted note →
OooOooOooh added! 🚀
What relay software ya runnin?
Proprietary (for now) and completely serverless.
Let me know if I can add anything to grain to make the decision easier to give it a try!
It’ll be released in due time, once all is clean and well tested 🫡
So cool— did not know that we are having relay issues but I certainly was— paid for Primal and then Nostr.wine when nothing worked on primal but now that relay does not work either…. So will try yours!
Can this be used in my DM relay list too?
Yes, inbox and all that is supported. Plus it also blasts your events to the other relays too.
Ok Google
Can it be used as proxy relay ?
Not based on Nosflare at all? 
I wonder if the LLM pulled from it lol
Nosflare - Next-Gen Nostr Relay
Deploy your own serverless Nostr relay in seconds with Cloudflare edge computing.
Not yet, but I may add that functionality
This is written in TS and with my general idea about the architecture. I did see and read nosflare code in the past, and I am aware of its adventures through architecture changes and different approaches. I would consider this to be inspired by nosflare for sure, but not based on it.
It's good that it's only for your paying members because the free relays are full of spam and ruining nostr.
Yes, Nosflare also written in TS 😉
You guys have a falling out with Nostr.land or something?
btw, if it is entirely DO based, get ready for a very expensive relay. I’ve been down this road already with an entirely DO-only architecture and it didn’t end well. Now, it’s just using DOs for handling websocket and broadcasting the events to subscriptions.
Not only that, but the cold starts of DOs can be problematic when they’re evicted and then hit with a SQLite or KV query. The current iteration of Nosflare is the best it could get imo. But would be curious to see what direction yours went.
That would be great
I’ve been working with DOs for a long time and am aware of their pros and cons for sure. While what you say is true, there are ways to work with them cost-effectively and fast. You just need to look at them as shards for storage, nothing more.
Eventually I’ll open source it once I tune the thing to scale and work properly, didn’t have much time to do that yet plus need to cleanup the code too.
Yes, the sharding is what was already tried, you can read about it in this (since) reverted readme 
GitHub
GitHub - Spl0itable/nosflare at 4896859710786b070c26f9dc6cfb6aa98a8604e1
A serverless Nostr relay through Cloudflare Workers and Durable Objects - Spl0itable/nosflare
I read it, yes.
NL: no, we didn’t have any issues with them, all good and still part of our plan offering for higher tiers. This relay is for all, not only higher tier customers
Nice
What does completely serverless mean in this context?
Means I don’t have a single server that I need to worry about or that any one failing will put it down
How does that work…Where is it running?
Asking genuinely to learn.
Think of it like AWS Lambda, or Google’s CloudRun, or Supabase functions, or Deno Deploy sort of thing. New mini “server” is spun up on new connection, and it works against common “database”
Interesting.
But how does that work with web sockets? Don’t relays require a persistent connection?
Nice — would love to use it and create a relay for indie animators— does it support short video clips?? #asknostr