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.
Login to reply
Replies (1)
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.