| Age | Commit message (Collapse) | Author |
|
|
|
NIP46 - update NIP44 calls
|
|
|
|
|
|
|
|
* New version of NIP-46
* Update pubkey references
* Document what we have
* Update terms and kind number in discovery
* Update encypt/decrypt calls to handle arrays. Add redirect_uri param for auth_challenges
* Move remote signer commands to own section, add appendix for oauth-like stuff.
* Add diagrams
|
|
* BREAKING.md: add NIP changes until 2023-12-01
* Update BREAKING.md
* BREAKING.md: add NIP changes until 2023-11-01
* Update BREAKING.md
* Remove change to NIP-22 in 2023-12-02
* BREAKING.md: add NIP changes until 2023-08-01
* BREAKING.md: add NIP changes until 2023-04-01
* BREAKING.md: add NIP changes until 2023-03-01
* BREAKING.md: add NIP changes
* Just format
|
|
|
|
|
|
* NIP-49 [breaking]: password normalized to unicode NFKC format
* Test vector for unicode normalization
|
|
* Start of new BREAKING.md changes list
* more
* Make NIP column into links
* notes
* Make commits links
* Remove optional P tag entry, was not breaking
* Update BREAKING with nip-49 breaking change
|
|
|
|
the current scheme recommends signing the *fingerprint* of the pgp key, which doesn't tie into the nostr identity
this commit temporarily undos the commit adding pgp identities until a proper fixed version is merged
just signing the npub string also would not be sufficient, and the message should indicate this is for identity verification
ideally, a link to download key material would also be included
|
|
|
|
* File metadata sets
* Make kind specific to release artifacts
* Update example
* Update README
|
|
Add kinds for NIP-59
|
|
|
|
fix(docs): typo in 01.md
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add imeta tag
|
|
|
|
|
|
|
|
|
|
NIP-59: fix typo and nitpicks
|
|
|
|
Add NIP-59 to README
|
|
|
|
Introduce NIP-59 gift wrap
|
|
* Key export/import as implemented by gossip
* Added test data
* Last push didn't make sense, only this direction works
* Multiple updates: 100k rounds, random salt, version number, length indications
* Rename to NIP-49, include in README
* Change encoding to bech32 (ncryptsec)
* Major rework of the algorithm. NIP is now incomplete as I haven't coded it yet.
* renamed
* spelling
* minor fix
* formatting
* MORE CHANGES: scrypt, spelt out more detail of the steps to take
* spelling
* Mostly just removing some unnecesary stuff
* Remove the cafebabe note
* Remove confusing nonce statement
* Change title (and a bit of wording)
* remove author
* remove legacy event
* rename on README
---------
Co-authored-by: Mike Dilger <mike@ezicheq.com>
Co-authored-by: fiatjaf_ <fiatjaf@gmail.com>
|
|
NIP-47: Nostr Wallet Connect Extensions
|
|
NIP-30: add supported kinds
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
its own
|
|
|
|
|
|
* Remove NIP-54 mention temporarily
* Update 96.md
Co-authored-by: arthurfranca <arthur.a.franca@gmail.com>
---------
Co-authored-by: arthurfranca <arthur.a.franca@gmail.com>
|
|
|
|
|
|
NIP-02, NIP-51: new tags should be added to the end of the list
|
|
* Add auctions to NIP-15.
* Update 15.md
Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>
* Address comments from @motorina0.
* Remove reference to removed type=10.
---------
Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>
|
|
Remove authors
|
|
|
|
* Add NIP-95 - File Storage
* Add missing response info
* Make it clear that is is an HTTP file storage server integration
* Add monetization suggestion
* Use zap split tags for monetization suggestion
* Add resize option
* Add Zap Gates Integration
* Replace /nip96 convention with /.well-known/nostr.json configuration
* Relays can choose to also act as HTTP file storage server
* Remove nip96 tag in favor of x tags third element
* Fix typo
* Remove redirect cooperation
* Replaced 422 with 400 status code
* Update 96.md
Co-authored-by: Jon Staab <jstaab@protonmail.com>
* Update 96.md
Co-authored-by: Jon Staab <jstaab@protonmail.com>
* Update 96.md
Co-authored-by: Jon Staab <jstaab@protonmail.com>
* Update 96.md
Co-authored-by: Jon Staab <jstaab@protonmail.com>
* Update 96.md
Co-authored-by: Jon Staab <jstaab@protonmail.com>
* Update 96.md
Co-authored-by: Jon Staab <jstaab@protonmail.com>
* Update 96.md
Co-authored-by: Jon Staab <jstaab@protonmail.com>
* Make file expiration a range and add terms_of_service
* Add optional content_type field
* Add plans and tos
* Remove monetization
* Apply minor fixes
* Update 96.md
Co-authored-by: Semisol <45574030+Semisol@users.noreply.github.com>
* Fix after review
* Add kind 10096
* Apply suggestions
* Add suggestions
* Remove duplicate field
* Add optional is_nip98_required plan config
* Add suggestions
* Replace x with ox tag for original file hash
* Make minor changes
* Remove nip96 namespace response field
* Add note about alternative file processing flow
* Simplify processing flow
* Add nostrcheck to server list
* Add audio/* example
* Explain what metadata to show before processing is done
* Add nostrage to list
* Add eta
* Add sove to list and replace eta with percentage
* Fix status code
* Add nostr.build to list
* Add sovbit
* Add optional extra http servers to ox tag
* Add void.cat to list
* Small fix
* Remove ox third array element
---------
Co-authored-by: Jon Staab <jstaab@protonmail.com>
Co-authored-by: Semisol <45574030+Semisol@users.noreply.github.com>
|
|
Update 51.md to add support for video lists
|
|
nip-46,nip-58: fix typos
|
|
|
|
|
|
|
|
|
|
Fix typos
|
|
|
|
|
|
Fix typos in 01.md and 50.md
|
|
|
|
|
|
Fixes https://github.com/nostr-protocol/nips/issues/958
|
|
|
|
Content in the summary tag is duplicated in the .content field
|
|
Fix typos of NIP-44
|
|
Amend NIP-52 to require the content field to be provided, and decouple calendar identifier from calendar name
|
|
Clarify JSON serialization for the `id` field
|
|
Co-authored-by: Pablo Fernandez <pfer@me.com>
|
|
Changed view start and end time to seconds
|
|
wish to use encryption can now use the new NIP-44 scheme.
|
|
|
|
|
|
Rephrase to "MUST" so that one does not assume a connection could `CLOSE` any `subscription_id`, which it must not.
|
|
Reword REQ for multiple filters
|
|
|
|
|
|
Add leading zero to NIP numbers
|
|
|
|
Emphasis on multiple filters in NIP-01
|
|
Clean up NIP 44
|
|
As mentioned further down in NIP-01
> A REQ message may contain multiple filters.
The comma makes it more clear that the message array can container more than 3 items. So it is understood easily to match
```
// correct:
["REQ", <subscription_id>, filters1, filters2, …]
```
instead of
```
// wrong:
["REQ", <subscription_id>, [filters1, filters2, …]]
```
|
|
Kind `2` was [consciously](https://github.com/nostr-protocol/nips/pull/703#issuecomment-1672098794) removed in https://github.com/nostr-protocol/nips/commit/72bb8a128b2d7d3c2c654644cd68d0d0fe58a3b1#diff-39307f1617417657ee9874be314f13aabdc74401b124d0afe8217f2919c9c7d8L105. Mentioning the fact should help prevent further confusion.
|
|
|
|
improve formatting and clarify encryption/decryption steps
|
|
|
|
|
|
|
|
* Introduce NIP-44 encryption standard
* Finalize NIP-44
* Update spec.
---------
Co-authored-by: Jonathan Staab <shtaab@gmail.com>
|
|
rewrite NIP-46
|
|
Adding segments
|
|
After discussing with Pablo, we decided to move away from relying on kind 1063 events and instead use the majority of the same tags for video events. The main motivations behind this are to allow for parameterized replaceable events for video events, prevent excessive `REQ` requests, not stringify event JSON in the `.content` section, ease of filtering by kind number, as well as some others. Happy to discuss this further.
|
|
Co-authored-by: Pablo Fernandez <pfer@me.com>
|