earliest-unique-commit r tag enables clients to:
- retrieve all repo events refering to a local git repo
- group repo events with different identifers that refer to same repo
- retrieve all patches for a local repo,
irespective of the tagged repo event
current-commit-id r tag enables clients to prevent accidental submission of a patch,
which has already been proposed
root-revision tag enables clients to filter out proposal revisions
from a list of proposals
can be used by clients to tag multiple maintainers in patches
helps clients identify whether multiple repo events for the same repository
are complementary or in competion
for consistancy and so that the intended order of patches is easier to ascertain
enables additional patches to be appended to a patch set, supporting a PR-like workflow alongside
patch-over-email-like workflow
It's very confusing as to whether it refers to remote user pubkey vs remote signer pubkey. This is complicated further by the typo in the explanation of "remote signer pubkey".
* NIP-34: git stuff.
* repository head.
* threads/issues and replies.
* add "p" optional tags to events.
* add list of things to do later in the end.
* multiple values in some tags instead of multiple tags.
* replace "patches", "issues" tags and replace that with "relays".
* bring in tags that allow for a commit id to be stable.
* edit "reply" kind to say it should follow normal NIP-10 threading rules.
* update "things to be added later".
* add commit time to "committer" tag.
* remove "head" tag.
* mention the possibility of mentioning others users in patches.
Co-authored-by: DanConwayDev <114834599+DanConwayDev@users.noreply.github.com>
* clarify commit-pgp-sig.
* clarify requirements and threading of replies.
* add t=root tag.
---------
Co-authored-by: DanConwayDev <114834599+DanConwayDev@users.noreply.github.com>
* NIP-29: Simple Group Chat.
* split hostname and subgroup path into two different tag items.
* add and remove permissions actions.
* fix kind number for moderation event.
* add missing / to "flavors" in example.
* some new ideas + making this universal and not only applicable to chat.
* fix delete-message => delete-event.
* flesh out the entire thing.
* saner approach with multiple kinds for moderation.
* delete-event as kind 9005.
* update meta events description.
* `public` and `open` tags and join request event.
* edit-group-status permission.
* add kinds to README.
* add kind:12
* add nip-10 note
* add optional list of members
* admins prefixed by "p".
* remove "alt" from event templates for brevity.
* add kind 10009 for public list of simple groups.
* update "previous" stuff.
* remove naddr stuff, use a different identifier format.
* remove reference to trimmed signatures until that is more developed.
* add kind:10 threaded chat replies.
---------
Co-authored-by: Pablo Fernandez <p@f7z.io>
* 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
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
* 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>
* 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>
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, …]]
```
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.
Adding some of Vitor's suggestions, differentiating between horizontal and vertical video kinds, changing how views are kept track of, and changing some tag names.
