Conversation
|
|
||
| ## NIP-19 entity | ||
| To create an `nchat` link: | ||
| - `kind`: `17` |
There was a problem hiding this comment.
kind is NIP number not event kind
There was a problem hiding this comment.
Why use the NIP number instead of just the chat kind?
There was a problem hiding this comment.
Yea maybe it makes more sense to use the kind number, originally i had the HRP as nchat17 and nchat28 but decided to change it last minute to use the kind entry.
| ## NIP-19 entity | ||
| To create an `nchat` link: | ||
| - `kind`: `17` | ||
| - `special`: one or more pubkeys concatenated |
There was a problem hiding this comment.
I think we should not concatenate but add all pubkey hexes in a TLV list (which is already been used for relays).
May need to note that the order of keys doesn't matter.
There was a problem hiding this comment.
We could have multiple special entries but idk if thats a problem for some clients
There was a problem hiding this comment.
May need to note that the order of keys doesn't matter.
Wouldn't that mean that there would be multiple equivalent entities for a single chat? That would be fine for some use cases, but it would be nice to have a unique ID for chats for use cases like this one
There was a problem hiding this comment.
It's going to be hard to trust people do this correctly, but we can request the list to be in ascending order by pubkeys.
But I would parse and resort it myself before doing anything with it.
| ## NIP-19 entity | ||
| To create an `nchat` link: | ||
| - `kind`: `28` | ||
| - `special`: `id` from `kind: 40` |
There was a problem hiding this comment.
Do we need nchat for public chats? I just use nevents as usual.
|
What is the point of this? Can't you chat with someone just from their |
It creates a link that apps can parse and send the user straight into a DM chat with a group of users. Very useful. |
Can also be used for NIP-29 chats with relay and |
|
I didn't know you were doing chats with groups of users. How do you do that? Maybe write that on the NIP then, because if it's with a single user only I don't see the point. NIP-29 chats can be referred to with an naddr very easily, I don't think this is necessary -- but I guess it can be used instead if it gets adopted. |
NIP-17 allows you to p-tag many people and send individual wraps to each of them. They define a group. It's like an email with many |
Its probably less important for web apps, but for native apps who want to link to nostr dms you cant really do it with npub because it would just go to profile, I use something like |
| The main limitation of this approach is having to send a separate encrypted event to each receiver. Group chats with more than 100 participants should find a more suitable messaging scheme. | ||
|
|
||
| ## NIP-19 entity | ||
| To create an `nchat` link: |
There was a problem hiding this comment.
A blank line is needed between 126 and 127 for expected rendering.
| ``` | ||
|
|
||
| ## NIP-19 entity | ||
| To create an `nchat` link: |
There was a problem hiding this comment.
A blank line is needed between 136 and 137 for expected rendering.
5 participants
To make it possible to create a link to a DM chat with another user we should add a new TLV HRP for chats