Inspired by the Build Your Own Adventure books, this NIP tries to emulate the same behavior on Nostr. It allows Clients to build button interfaces ...

This proposal does NOT (necessarily) replace kind:3, it's a way to do a very simple follow of one or more kinds that might be of interest. A us...

This NIP defines a specification for organizing nostr events into collections - ordered, optionally-hierarchical structures like books, journals, o...

I have zero experience developing for Nostr, and I probably did more things wrong than right, but this was my best attempt at expressing my ideas. ...

This is a variant of #1589 which attempts to reconcile NIP 29 and flotilla's rooms over chat and thread kinds. This requires no changes of NIP ...

This is an alternative to NIP 29. Here's why I'm going this direction: NIP 29 is over-prescriptive in several ways. The most obvious examp...

Motivation Nostr decouples applications completely from the transportation layer, meaning services no longer have to be designed around a single tr...

Abstract This proposal addresses the issue of misleading or deceptive edits to static media content (in event contents), often used to exploit emot...

Summary This proposal defines a new event kind for Nostr to represent and share food recipe metadata. It aims to provide a standardized format for ...

Read here I think this way won't break regular kind:1 clients. It is similar to using d tag but won't make chronological feeds see the edited note ...