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 (15)
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 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.
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.
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
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”
It’s a relay, so it’s all JSON and text. NB supports short videos, of course