Nostr Proxy: see you in 6 hours It looks better, a lot

This is my main issue on Nostr Proxy. After running for ~1 hour (locally) with 15-20 clients connected to it, I closed all clients. Everything got cleaned correctly, but not these Promises. 534k Promises... That's why Nostr Proxy crashes after a while. If anyone can help with this analysis, contact me please. I can't find any information in the memory heap snapshots

Nostr Proxy stress test time! https://nproxy.zerologin.co or https://nproxy.cc (or both)

Welcome sir #[0] Did you remember twitter? It was an old social network back in the good old days

Is it a good UX to always have to click on "Show X new notes" instead of displaying them directly in the thread?

I'm on iris.to. Let's try it

Oh, I found a beautiful memory leak in nostr-tools! Fixed on my branch, let's try this!

GM it crashed again

Nostr proxy is running for more an hour without RAM or CPU issue! If it stay alive all the night, I could say it's "stable". Try it here https://nproxy.zerologin.co (deployed on a VPS) https://nproxy.cc (deployed on railway) Stats are funny (no) VPS: 20 currents connections - 50-100Mo RAM Railway: 2 currents connection - ~140Mo RAM

GM This morning, I have an idea for Nostr Proxy. Is it required for the proxy to validate schnorr signatures for each events? Because stored events in relays are already validated and client validate events too when getting them. So... is it required for the proxy to validate them? Schnorr signature validation is really CPU intensive. It validates ~5000 events/min when opening 7 global feeds.

Can you please try wss://nproxy.cc instead of wss://nproxy.zerologin.co Not definitive, but it's deployed elsewhere

Ok, time to deploy the new relaypool to https://nproxy.zerologin.co Stress test incoming!