Damus
Quentin profile picture
Quentin
@quentin

Developer, libertarian, and Bitcoin HODLer. Lover of Nostr and Blossom protocol. Building a piece of Nostr. Always in search of restless minds.

Relays (12)
  • wss://purplepag.es – read & write
  • wss://nos.lol – read & write
  • wss://relay.damus.io – read & write
  • wss://relay.mostr.pub – read & write
  • wss://nostr.wine – read & write
  • wss://relay.primal.net – read & write
  • wss://relay.nostrcheck.me – read & write
  • wss://relay.nostr.band – read & write
  • wss://pyramid.fiatjaf.com – read & write
  • wss://offchain.pub – read & write
  • wss://lang.relays.land/es – read & write
  • wss://relay.npubhaus.com – read & write

Recent Notes

quentin profile picture
You need to create more users in ‘Registered users’ tab on the dashboard. Then they will be able to write and read to the relay. Thanks for using it!!
quentin profile picture
Finally, I’ve just released version 0.7.0 of nostrcheck-server.

It’s been months of hard work, and I’m proud to deliver the best release this project has ever had. The highlight: the integrated Nostr relay and full multi-tenancy support.

Changelog 0.7.0

- The Nostr relay (Brand new, built from scratch with full NIP support)
- Multi-tenancy support (different domains, different configs, one instance)

- Improved security engine.
- Improved database engine.
- Improved Redis engine.
- New log engine.
- Enhanced AI moderation engine.
- Legal, privacy and TOS pages.
- Refactored dashboard and settings page.
- Custom file types and extensions.
- Improved theming engine.
- Tons of new configurable options.
- Key converter frontend page.
- Relay frontend page.
- Improved install script.
- General refactor and code cleanup.

Thanks to everyone who has followed the project and provided feedback. Available as standalone and Docker install. Enjoy! 🥳

https://github.com/quentintaranpino/nostrcheck-server
quentin profile picture
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. 🫂💪💜
quentin profile picture
Do you want to try a completely new relay that isn’t based on any existing implementation? I’m working on this:

wss://playground.nostrcheck.me/relay

#nostrdev
quentin profile picture
150,000 files uploaded to nostrcheck.me just a few days before its second anniversary. Slow but steady steps, we are always on the side of freedom and sovereignty 💪🤓



I hope to offer this service for many more years!! 🥳

#nostrcheck
quentin profile picture
The latest Damus update implements the PR I submitted a few weeks ago to add nostrcheck.me as a file hosting service. It’s been a long journey, but it’s now a reality 🥳😀. Thank you Damus team 💜

#nostrdev #nostrcheck #damus
quentin profile picture
This morning someone uploaded the 40000th file to nostrcheck! 🎉🎉🎉



40,000 files uploaded and only 9GB of data used. I am sure we are the most data saving media provider, both on the server side and on the client side.

Many congratulations to the person who uploaded this beautiful image that vibrates on the same frequency as us 💜💜💜
quentin profile picture
I think one of the most important challenges in nostr is going to be about the servers that host files, and we are not devoting enough attention to it.

Right now there are 5 of us (as far as I know)

nostr.build
void.cat
nostrimg.com
nostrfiles.dev
nostrcheck.me

I believe that self-custody of files should be encouraged as soon as possible so that anyone can host their own files on their own server (at home for example).

In this way, NIP-96's proposal together with more users installing nostrcheck.me on their home servers is the solution to the centralization of this important part of the protocol.

https://github.com/nostr-protocol/nips/pull/547

I would like that this proposal can prosper to adapt my server to its specifications and finally get that many nostr users never again depend on anyone to share their own files in a sovereign way.

If anyone is interested in collaborating, here is the code.

https://github.com/quentintaranpino/nostrcheck-api-ts/

In case someone didn't know it, the goal of nostrcheck.me is to be used locally by many people and then step aside so that no one will ever again have to depend on a service provider for their own nostr address, file uploads and all the other services implemented on the server, if anyone has doubts why nostrcheck.me offers all its services for free, I guess they finally know what is its ultimate goal, to disappear to make way for thousands of sovereign nostrcheck.me.