Quentin

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 🥳🥳

Did you know that nostrcheck.me is natively supported and integrated into all these Nostr clients? Nostrudel Amethyst Snort Nostur Damus Coracle Nostrid Openvibe Nostter Freerse Olas Iris (I just sent a PR today to add it!) 💪 (And many more that I can't remember 😅) Simply select it in the options of your favorite app, and you'll be able to start uploading your files instantly! You can create a free account here: 👉 https://nostrcheck.me/register By the way, even if you don't have an account, you can still use our server for free! (You'll miss out on file management options, but if you decide to register in the future, you'll regain access to all the files you've uploaded.) 🥳🥳🥳

I receive hundreds of images and videos every day. Only a small fraction of these uploads contain unpleasant, illegal, or outright revolting content. However, even this small fraction carries significant weight. Due to my daily reviews, I am beginning to experience flashes of disturbing images. Reviewing content every day takes its toll, and hosting providers take on a personal risk by storing other people’s files so that Nostr can thrive and more independent servers can emerge. Over the past two years, I have hosted close to 200,000 files. Thanks to some donations, I have been able to keep going, and I truly appreciate that support. But let’s be honest: relying on individual resilience is not a sustainable model. Running a media server at no cost is already a challenge, and on top of that, there are structural barriers that make it even harder. While some servers are included by default in new clients, others, like mine, despite having been early adopters of key standards such as NIP-98, NIP-94, NIP-96, and later Blossom, struggle to gain visibility. Instead of an open and natural selection process, inclusion often depends on persistence, PRs, and constant requests. This is not just about one server or one person. If running a media server in Nostr means constant hurdles and limited opportunities for integration, many simply won’t take the leap. And that is why we have yet to see a real explosion of Blossom or NIP-96 servers. It’s encouraging to see some progress in the right direction, at least from my perspective. My PR to integrate BUD-07 (Paid Upload and Download) into Blossom seems to be getting closer to approval, which could help smaller servers sustain themselves through microtransactions. While larger servers already have subscription models outside of Nostr or Blossom that allow them to remain operational, this new implementation could provide a real opportunity for those looking to operate without relying on external funding. A reflection for nostr client maintainers: If we want a truly decentralized and resilient ecosystem, we must avoid closed systems that prevent users from adding custom servers. Recommending media servers statically limits diversity and discourages innovation. Instead, let’s use Nostr itself to discover the servers people are actually using and recommend them dynamically based on the user’s needs. We have the tools to make this work—let’s use them! Happy Sunday, #nostr. I’ll keep building what’s unseen but still used. 🫂💪💜

https://cdn.nostrcheck.me/89e14be49ed0073da83b678279cd29ba5ad86cf000b6a3d1a4c3dc4aa4fdd02c/3461fad79b70fd465e4b54f9119e3d90759020f121e20e568e04c3fdd347df5f.mp4

I’ve been receiving warning messages about a misconfigured Lightning redirection. It belongs to a pubkey registered on nostrcheck.me. I’ve tried reaching out via DMs, notifying them so they can fix it, but I haven’t received any response. Meanwhile, I keep receiving these errors daily. Since I have backend access, I could manually change this redirection to a valid LN address. However, this raises some ethical and practical questions: Do I have the legitimacy to do this? Who or what organization should these sats be redirected to? Should I leave the error as is indefinitely, or should I find a better place for these sats? Would it be acceptable to temporarily redirect them to a valid LN address and hold them until I get a response? My first instinct is to leave everything untouched, but I’d love to hear Nostr’s thoughts on this 🤓 #asknostr #nostrcheck

Nostrcheck-server now officially supports NIP-62. nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3qamnwvaz7tmwdaehgu3wd4hk6tcqyprqcf0xst760qet2tglytfay2e3wmvh9asdehpjztkceyh0s5r9cpvx58v https://github.com/quentintaranpino/nostrcheck-server/commit/334eede5e02033021695b1d0a4941b568bc5e3fa

Nostrcheck-server live status demo #nostrdev #nostrcheck #relay https://cdn.nostrcheck.me/89e14be49ed0073da83b678279cd29ba5ad86cf000b6a3d1a4c3dc4aa4fdd02c/1795645af7b89f66c3e3d424eedd51d8a6a7acb057dd4769a48e79ad149b6003.mp4

10 years of evolution.

How is it possible that some clients still don’t support NIP-42?? Am I missing something? To me, it’s a super elegant solution for authenticating ws connections.

Relay almost done, testing 🤓 #nostrcheck #nostrdev