Proposal

Add native Nostr protocol support in Flare, enabling users to publish and consume content via Nostr relays.

Motivation

Flare currently aggregates feeds from platforms such as Mastodon, Bluesky, Misskey, X, and RSS. By integrating Nostr, Flare can:

• Connect to a growing decentralized pub-sub ecosystem.
• Allow users to post and consume Nostr content (events, reactions, zaps) alongside existing federated feeds.
• Provide cross-protocol interoperability, enabling shared posting and multi-client access.

Suggested Features

1. Relay connection

   • Connect to public or user-specified Nostr relays
   • Subscribe to event kinds such as notes, reactions, and metadata

2. Publishing

   • Support publishing Nostr Kind 1 (text), Kind 42 (long-form), and video-related NIPs relevant to Flare’s video features

3. Interactions

   • Enable liking, zapping, and replying using standard Nostr event kinds and NIPs (e.g., NIP-25 replies, NIP-65 zaps)

4. UI integration

   • Add Nostr feed timelines and publishing forms consistent with existing interfaces

5. Account onboarding

   • Provide sign-in via NIP-07 or NIP-46 and local private key management

Benefits

• Expands Flare’s reach into the decentralized content network.
• Enables seamless cross-client publishing and feed aggregation.
• Aligns with existing video-centric use cases (e.g., Flare’s support for Nostr video events).

Considerations

• Should Nostr integration be enabled by default or remain opt-in?
• How to handle relay discovery, selection, and moderation?
• Should user-hosted relays be supported in addition to public ones?
• What moderation policies or filters should be applied?

References

• [Nostr protocol specifications and NIPs]
• Existing Nostr video event implementations relevant to Flare