Avatar
STERRY
f377b708adc4343cdd2e60ea46c683f25079f757e51204cee381de0f65726648
Explorer and early adopter, painter, musician, coder, movie buff, bitcoiner, family man.

Not 100% sure about color coding but added quick links divided by status at the top of https://codeberg.org/nostr/nip-index/src/branch/main/README.md

Very neat! nostr:npub1xhe9408d5hm3dpwax78sy9nuc5warycnvcy4r3qzv6jacwu26r6s5m56yf As a sort of gutcheck on how chaotic nostr is in the wild versus what the protocol says I'm trying to find out what % of messages are of kinds listed in https://github.com/nostr-protocol/nips/blob/master/README.md versus not.

Would you be so kind as to run a count by kind for say the last week on your crawler's data?

Is there a place to find all the kinds in use in say the last 24 hours or week? #asknostr #nostrdev

Question for those of you who follow NIPs. A project called nostrocket has created its own repo called NIPS and is requesting a kind it uses be included in the canonical NIPs readme. To wrap my head around all the various NIPs in various states, I started maintaining a list of NIPs in various states so here's the question...

If you were maintaining such a list, what criteria if any would you use for including protocol documents related to nostr outside the canonical NIPs repo? Is a repo enough? Does it need implementation(s)? Stars?

https://github.com/nostr-protocol/nips/pull/867

#nips #nostrdev #protocols #standards

Sort of. It seems to be a standard so you can have one app manage keys and signing, and other apps on the same device can talk to it to request signatures.

New NIP proposed...

(unmerged)NIP-100: Android Signer Application

This NIP describes a method for 2-way communication between a android signer and any Nostr client on Android. The Android signer is an Android Application and the Client can be a Web Client or an Android Application.

https://github.com/nostr-protocol/nips/pull/868

NIPs Repo Status

------------------------

Total indexed NIPs: 135

Unmerged draft NIPs: 78

Merged draft NIPs: 49

final NIPs: 6

Generated by nip-index

https://codeberg.org/nostr/nip-index

New NIP merged...

NIP-84: Highlights

This NIP defines kind:9802, a "highlight" event, to signal content a user finds valuable.

https://github.com/nostr-protocol/nips/blob/master/84.md

NIPs Repo Status

------------------------

Total indexed NIPs: 134

Unmerged draft NIPs: 77

Merged draft NIPs: 49

final NIPs: 6

Generated by codeberg.org/nostr/nip-index

Replying to Avatar STERRY

New NIP proposed...

(unmerged)NIP-110: License Tag

This NIP defines how to add licenses to Nostr events.

https://github.com/nostr-protocol/nips/pull/857

NIPs Repo Status

------------------------

Total indexed NIPs: 134

Unmerged draft NIPs: 78

Merged draft NIPs: 48

final NIPs: 6

Generated by codeberg.org/nostr/nip-index

It seems to be for adding a license to any Nostr event. This might be for content creators who want or need to have clear licenses on their work. It's a common concern in decentralized systems.

New NIP proposed...

(unmerged)NIP-110: License Tag

This NIP defines how to add licenses to Nostr events.

https://github.com/nostr-protocol/nips/pull/857

NIPs Repo Status

------------------------

Total indexed NIPs: 134

Unmerged draft NIPs: 78

Merged draft NIPs: 48

final NIPs: 6

Generated by codeberg.org/nostr/nip-index

New NIP proposed...

(unmerged)NIP-88: Recurring Subscriptions

This NIP defines a way for a pubkey to create recurring subscription payments to another pubkey.

https://github.com/nostr-protocol/nips/pull/866

NIPs Repo Status

------------------------

Total indexed NIPs: 134

Unmerged draft NIPs: 78

Merged draft NIPs: 48

final NIPs: 6

Generated by codeberg.org/nostr/nip-index

It's great to see all the feedback and discussion here on Nostr itself! I plan to go through and see what's represented in the GitHub issues and try to reproduce or enter what I can. https://github.com/hzrd149/nostrudel/issues

What is the closest thing to nostr that isn't nostr? I'm wondering about precursors, offshoots, different implementations of the same core principles? #asknostr

GM 👫👫👫👫 Once upon a time I was watching a live stream with 900 viewers and wondered what that'd look like if they were all in a single audience. Here's the result.

New NIP proposed...

(unmerged)NIP-100: Default Relay Port Standard

This document standardizes the default network port for Nostr relays, each relay can serve it services on `4444` port as default.

https://github.com/nostr-protocol/nips/pull/852

NIPs Repo Status

------------------------

Total indexed NIPs: 132

Unmerged draft NIPs: 77

Merged draft NIPs: 48

final NIPs: 6

Generated by codeberg.org/nostr/nip-index

noStrudel just added a create button in the Communities view. Didn't try it but it looks good.

Yeah hoped to express the similarity in your proposal to OAuth

NIP-90: Data Vending Machines in `draft` status was just merged.

This NIP defines the interaction between customers and Service Providers for performing on-demand computation.

Money in, data out.

https://github.com/nostr-protocol/nips/blob/master/90.md

NIPs Repo Status

------------------------

Total indexed NIPs: 130

Unmerged draft NIPs: 75

Merged draft NIPs: 48

final NIPs: 7

Generated by codeberg.org/nostr/nip-index