-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[arcade-chat] Basic chat channels+messages flow works #28
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
What do you think of
i.e. the channel id is the id of the channel creation event. I don't see the need for a "channel join" event, but maybe that is useful only for cosmetic purposes. kind 41 could be "channel metadata", similar to kind 0, but for setting a name, description etc for the channel. |
Another thing I was thinking is that it should be made clear that this is for public channels, since private channels would require a much more involving cryptographic protocol (that I personally am not sure it should even be done on Nostr). |
I get channel create, but why can't channel messages be simple nip10 threads + kind1? Seems like another missed opportunity for interoperability. |
@jb55 don't you think it is better that clients opt in to show these messages? It is easy for them to just specify |
yes a different kind isn't the problem. as long as chatrooms follow nip10 then it should be trivial to make it interoperate in damus. |
Cool - updated code here uses NIP10 tags for channel ID and event kind 41 for channel metadata. Will firm up the API and release a test build in a few days, then will draft a NIP and ask feedback on that. |
ah looks like 42 are json blobs so this isn't as simple as treating type 42 notes like type 1 notes :( I guess these will just be separate from the rest of text nostrverse for now. |
kind 42 suggestions: nip10 support to me would mean:
|
Yes, please, just the text! |
Picture of in-channel message UI
Experimental Nostr chat support, adding message types 40 (channel create) and 42 (channel message). Envisioning that 41 will be channeljoin, and 43-4X will be various channel moderation events.
Most relevant logic is in:
This implementation is probably too simple, with channelId set in the content field. Should probably be a NIP-10 tag?
Open to feedback on how to restructure this to maximize interop with other event types if appropriate.
Relevant types currently:
Link to discussion in Nostr Telegram