I'm planning to write a c# implementation of Negentropy, any tips? @npub1yxpr...qud4 Is it a good idea to draw inspiration from the js implementation? The ultimate goal is to support NIP-77 in my #netstr relay

I think your last point is spot on, but also probably the hardest for some people, especially devs who see their product (code) as their baby they need to nurture. And when others are spitting on it, critisizing it and bending it backwards they tend to take it personally. It takes time to move one's mental state from "it's mine" to "it's ours and I am no better than anyone else"

#netstr is live! Running on https://relay.netstr.io/ and wss://relay.netstr.io 🎉 #nostrdev #relay #growstr #nostr

#netstr first release is approaching, today I finished rewriting how events are broadcast to clients, should be much faster now, especially in an environment where you have many events being sent. Almost all relays suffer a race condition where if you're establishing a new subscription they will either miss events just being sent or they will send them before EOSE. Netstr now deals with this. I'll focus on DB optimizations and other stability improvements now. But I'm looking forward to some more NIP implementations, e.g. Request to Vanish, support for AND tag conditions, negentropy, and others. Stay tuned.

GitHub

GitHub - bezysoftware/netstr: Modern nostr relay

Modern nostr relay. Contribute to bezysoftware/netstr development by creating an account on GitHub.

Dev version is deployed at relay-dev.netstr.io feel free to connect 🎉

#netstr is running on dev, and it's awesome 🎉 #nostr #relay #nostrdev

Autumn is here 🎉

@Relayable.org can you share him much space your relay DB takes? I want to deploy my own public relay, any idea how much I can expect? Assuming it becomes popular