37cf601c01
This commit supports multiple naddrs for sending issues to and searching for repositories by extracting the embedded relays, and appending to the address file instead of overwriting its previous contents. A header has also been added to the `nostr-address` file to clarify its purpose. This enhancement accommodates maintainers who distribute issue tracking across multiple repositories, preventing confusion if the primary maintainer steps down. Now, issues and patches will reference all relevant repositories, not just one. Note that repositories won't automatically include all maintainers' addresses unless explicitly specified. Maintainers may manage a repository under a project-specific public key rather than individual keys. Addresses are only added to issues and patches when explicitly provided via the command or written to the address file. This prevents unintended inclusions and ensures clarity. Suggested-by: DanConwayDev <DanConwayDev@protonmail.com> Signed-off-by: Awiteb <a@4rs.nl>
!!! warning "Work In Progress" This project is still work in progress and not completed yet.
n34
A CLI to interact with NIP-34 and other stuff related to codes in nostr
About
n34 is a command-line interface (CLI) tool for sending and receiving Git
issues, patches, and comments over the Nostr protocol. It supports creating,
replying to, and managing issues and patches, making Git collaboration
decentralized and censorship-resistant.
The primary goal of n34 is to implement NIP-34 (git stuff), but its
flexible design allows for additional use cases beyond Git workflows. For more
details, see the following section.
Features
- Repository announcements
- Repository state announcements
- Patches
- Issues
- Replies
- Status
- Gossip Model (NIP-65)
- Proof of Work (NIP-13)
nostr:URI scheme, in the issue/reply content (NIP-21)- Code Snippets (NIP-C0)
- In device relays and repos bookmark
Why Nostr?
Nostr is fundamentally different from traditional platforms because it’s not an application or service, it’s a decentralized protocol. This means any tool or app can integrate with it, enabling open, permissionless collaboration without relying on centralized gatekeepers. Unlike proprietary systems, Nostr doesn’t require emails, passwords, or accounts. You interact directly through relays, whether you self-host your own or use public ones, ensuring no single point of failure or control.
What makes Nostr uniquely resilient is its design, the protocol itself is just
a set of rules, not a company or product that can disappear. Your Git issues,
patches, and comments persist as long as relays choose to store them, immune to
the whims of corporate shutdowns or policy changes. Nostr is infrastructure in
its purest form, an idea that outlives any temporary implementation. n34 taps
into a future-proof foundation for decentralized collaboration.
More about Nostr
Contributing
Contributions to n34 are welcome! You can help by opening issues (such as bug
reports or feature requests) or submitting patches. All contributions must be
submitted through Nostr. For more details on the process, please refer to the
CONTRIBUTING.md file. Your support is greatly appreciated!
Contributions & Changes
You can find the changelog at CHANGELOG.md and the list of contributors at AUTHORS file.
License
n34 is licensed under the GPL-3.0 License. This means that you are free to use, modify, and distribute the software under the terms of this license. Please refer to the LICENSE file for more details.