Hey #Nostr I am extremely happy to unveil another major update to the #Nosflare relay implementation. After much testing, I have been successful in refactoring to Typescript as well as integrating Durable Objects for real-time delivery of events. This creates a true websocket connection and will broadcast new events to all connected clients. I know there have been a lot of updates lately, so I am sorry if you've forked to build your own relay. But, I promise you this update to v7.0.0 is entirely worth it and the build process is nearly identical.
Gotta love it when a new Nostrich joins from legacy social media and you respond to welcome them, zap them, and don’t even get a response back lol. Not saying I deserve their attention or anything, but just strikes me as odd.
Welp, I was successful in not only refactoring Nosflare into typscript, but also linking it through Durable Object to create websocket state cooridination (in order to broadcast new events to all clients in real-time), but this creates such a bottleneck and extra hop that the trade-off in speed is not worth it. Basically, with the current iteration of Nosflare, due to Workers being stateless, the websocket state doesn't entirely work so the Workers runtime eventually just force kills the hung worker after 2min. This is pretty much fine as it doesn't impact the actual relay functionality (and I'd be worried if it really took more than 2min to do anything anyway), but it just means the error rate in logs is a false-positive as it looks like 99% lmao
