# Nostr: Why do features work in one Nostr client but not another?

Clients choose which NIPs to implement and how to present them.

2026-08-16
::
Switchboard Tech Services


![Nostr: Why do features work in one Nostr client but not another?](https://switchboardtechservices.com/static/images/defaults/guides.webp)

## Short answer

Clients choose which NIPs to implement and how to present them. A relay may also lack support for a requested feature or may reject events under its rules. Compare the client's feature list, relay capabilities, and the relevant NIP before assuming a bug. Your public key can travel between clients, but the interface and supported event kinds need not match.

## Sources

[Nostr Improvement Proposals index](https://github.com/nostr-protocol/nips/blob/master/README.md), [NIP-11: Relay metadata](https://github.com/nostr-protocol/nips/blob/master/11.md).

- Categories:
  [Nostr](https://switchboardtechservices.com/guides/categories/nostr/)
- Tags:
  [#troubleshooting](https://switchboardtechservices.com/guides/tags/troubleshooting/), [#Nostr](https://switchboardtechservices.com/guides/tags/nostr/), [#Decentralized Social](https://switchboardtechservices.com/guides/tags/decentralized-social/), [#Open Protocols](https://switchboardtechservices.com/guides/tags/open-protocols/)

[Guides RSS](https://switchboardtechservices.com/feeds/guides.xml "Subscribe using an RSS reader")

---

Canonical URL: https://switchboardtechservices.com/guides/nostr-why-do-features-work-in-one-nostr-client-but-not-another/

Language: en-us

Content type: guide

Author: Switchboard Tech Services

Published: 2026-08-16T19:32:36+00:00

Description: A practical answer to Why do features work in one Nostr client but not another?