Good to hear that more people are aware that Buzz is not a "real" Nostr client and is missing a lot of Nostr best practices. I think the project is currently not aiming at nostriches as an audience, so there is a lot of low-hanging (nostr) fruit there to be implemented in the client. This could be a perfect opportunity to get in touch with other developers who are contributing to the project who don't know what Nostr is. What do you think @Sync @Eric FJ 🪬⚡️ @Gzuuus @NOVA? I see that @Alex Gleason and @Leo Wandersleb is already doing some work there

GitHub

[Bug] Mentions should use NIP-27 · Issue #2319 · block/buzz

Currently mentions are not interoperable with other Nostr clients. It's fine to type @username in the text box, but after hitting submit the event ...

GitHub

Request: use Ditto Theme kind for theme events · Issue #5285 · block/buzz

Motivation This is a Nostr interoperability request for Buzz compatibility with other Nostr clients. Proposed solution Buzz switches from NIP-78 th...

GitHub

feat: Support NIP-46 Remote Signing aka nsec bunker · Issue #2700 · block/buzz

Exposing private keys to different clients is a dangerous pattern clients should not encourage. If at all feasible, the app should build on remote ...

This is very early issue about this topic

GitHub

Make Sprout a standard-compliant Nostr relay alongside its enterprise extensions · Issue #265 · block/buzz

Summary Sprout uses the Nostr wire protocol (NIP-01) and extends it with enterprise features: NIP-29 relay-based groups, workflows, canvases, forum...

when Buzz still was named as Sprout.