I’m looking for someone reliable to help manage nostrcheck.me while I’m unable to do it myself. I don’t charge for hosting the content, this is a volunteer effort, and the same applies to this role. Without daily reviews of the files rejected by the AI model, nostrcheck.me won’t be sustainable in the medium term. If you’re interested in helping or know someone who might be, please reach out.

Still here 🫶

GM #nostr

0.7.0 drops after docs. 0.8.0 might mint something interesting 🤓

Thank you @brugeman for you time and patience. My relay is almost done!! 🥳🥳🫂

Code over ego. Always.

Hello #nostr . Could you please add the relay from nostrcheck.me and keep it in your list of relays for a few days, even if it experiences some downtime? I'm looking for more users to help run a realistic stress test. wss://relay.nostrcheck.me A billion thanks! 🙏💜

Almost 100 stars on GitHub, thank you! 🙏🥳💜

GitHub

GitHub - quentintaranpino/nostrcheck-server: The community’s Nostr brain: The only server with relay, File Hosting (NIP-96 & Blossom), Nostr Address (NIP-05), Lightning Redirects, NWC, WoT, and much more.

The community’s Nostr brain: The only server with relay, File Hosting (NIP-96 & Blossom), Nostr Address (NIP-05), Lightning Redirects, NWC, WoT, ...

I’m in England, and I just can’t understand how they manage to drive completely the other way around!! 🤣🤯😱🤓🚙🫂💜

This relay is bringing out both the best and worst in me at the same time 😅🤓🤣 I’ve finally solved a memory management issue for heavy REQs—I’m pushing the limits of what TypeScript allows me to do.

Did you know that besides nostrcheck.me, we also have these three domains? nostriches.club (Invite-only) plebchain.club (Invite-only, paid) nostrverse.net (Paid) The paid domains use NWC technology to calculate the cost based on the length of the username. If anyone wants an invite for nostriches.club or plebchain.club, let me know, and I’ll send it via DM! 🥳🥳🥳

I’m almost done with the new relay for nostrcheck-server, currently experimenting with search extensions. So far, it’s stable and fast with 3,000,000 events loaded into memory. I had to fine-tune every operation to avoid bottlenecks across the system. Querying such a large dataset is inherently slow, but on top of that, the relay has to handle hundreds of simultaneous requests over open WebSockets. To tackle this, the relay currently runs with a pool of n workers and a processing queue for heavy tasks. It’s fully compatible with all relevant NIPs. Not designed for 100 million events yet, but more than capable of efficiently handling community-scale needs. I’m sure I’m running into the same problems others have already solved, but I’m doing it anyway—because this is Nostr. We have to keep 500 incomplete and incompatible clients connecting to 500 incomplete and incompatible relays, otherwise, what are we even doing here? 🤣🤓 Good morning #nerdstr 🥳🥳