Skip to content

[REQUEST] NIP-50 relay support for keyword search #262

Closed

Description

@ghobs91

Describe the solution you'd like
NIP-50 relay support for keyword search as described here: https://github.com/nostr-protocol/nips/blob/master/50.md

Activity

  1. changed the title [-][REQUEST][/-] [+][REQUEST] NIP-50 relay support for keyword search[/+] on Mar 13, 2023
  2. a-khushal commented on Apr 17, 2026

    @a-khushal
    Contributor

    @cameri is this up for grabs? can i work on this issue?

  3. cameri commented on Apr 18, 2026

    @cameri
    Owner

    I believe this is one of the project ideas for SoB. Let's hold off for now.

  4. Mahmoud-s-Khedr commented on May 9, 2026

    @Mahmoud-s-Khedr
    Contributor

    @cameri I would like to work on this over the next week.

  5. cameri commented on May 9, 2026

    @cameri
    Owner

    Thanks for the interest @Mahmoud-s-Khedr . Assigned to you.

  6. Mahmoud-s-Khedr commented on May 16, 2026

    @Mahmoud-s-Khedr
    Contributor

    @cameri I've finished the implementation and local integration testing for NIP-50. Before I open the PR, I want to run external e2e tests against the relay to ensure strict client compatibility. Is there a specific NIP compliance tester or external e2e suite you prefer? I was thinking about running a Nostr client, but this will take a bit more time, and I'm approaching my practical exams, so I wanted to get your opinion on the best approach.

  7. cameri commented on May 24, 2026

    @cameri
    Owner
  8. Mahmoud-s-Khedr commented on May 24, 2026

    @Mahmoud-s-Khedr
    Contributor

    Hi @cameri, I will be looking at it. My main concern is the quality of NIP-50 extensions like Spam and language detection. I do not want substandard implementation for them so I was looking for a test suit for them. I have finished my practical exam and will be looking more into NIP extensions and how I can improve their quality.

  9. Mahmoud-s-Khedr commented on Jun 6, 2026

    @Mahmoud-s-Khedr
    Contributor

    Hi @cameri, it took a while, but I found this relay as a reference: https://github.com/atrifat/nostr-filter-relay. It uses dependencies built by the author that are based on open-source models. The current problem is that these models require more resources to run, and one of my main goals is to avoid making the relay resource-hungry.

    Because of this, my current plan is:

    • Ship just the core NIP-50 search in the first PR.
    • Create a second, separate PR for the extensions, making them strictly optional so that whoever runs the relay can enable or disable them as needed.

    What do you think about that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions