jb55 -- 137d > You might need a NIP-22-like root event kind to set the topic and then people cite it to group. that's what i was thinking. like the message-id in email reply> You might need a NIP-22-like root event kind to set the topic and then people cite it to group. that's what i was thinking. like the message-id in email
thread · root 01ddd8ac…46cf · depth 14 · · selected bcc4a155…9458
thread
root 01ddd8ac…46cf · depth 14 · · selected bcc4a155…9458
Do NIP-17 DM app enjoyers utilize one-on-one chats, group chats, or both?cc nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqnnostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5znostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wlnostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxgnostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknprnostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445
Which can do group chats?
Here is an imperfect tracker: https://github.com/nostrability/nostrability/issues/169
So only Flotilla and Coracle?
nostr:npub1gm7gw8q6akeft2pjt270we35vlff0v9g2fene6cxkz2h68q5hl6qls0fte too
And nostr:npub1tm99pgz2lth724jeld6gzz6zv48zy6xp4n9xu5uqrwvx9km54qaqkkxn72
Amethyst does group chat too
Issue that nostr:npub1fgz3pungsr2quse0fpjuk4c5m8fuyqx2d6a3ddqc4ek92h6hf9ns0mjeck is running into:> another thing I find broken with chatroom is you can't have multiple chats with the same set of people, theconversations would simply combine
Yep, that's by design
we'll support it but feels like a bad design, whats the use case ?
To keep it simple. Topic-based approach has way too many edge cases that needs to be dealt with.
makes sense
The issue is to avoid grouping things with the same subject that are not supposed to be grouped, like 2 "Dinner"conversations with different people OR one year apart from each other.You might need a NIP-22-like root event kind to set the topic and then people cite it to group.
> You might need a NIP-22-like root event kind to set the topic and then people cite it to group.that's what i was thinking. like the message-id in email
Which can do group chats?
elsat -- 137d [parent] | reply [1 reply]Here is an imperfect tracker: https://github.com/nostrability/nostrability/issues/169
dab6c606…07b6 -- 137d [parent] | reply [1 reply]So only Flotilla and Coracle?
7fa56f5d…c194 -- 137d [parent] | reply [1 reply]nostr:npub1gm7gw8q6akeft2pjt270we35vlff0v9g2fene6cxkz2h68q5hl6qls0fte too
elsat -- 137d [parent] | reply [1 reply]And nostr:npub1tm99pgz2lth724jeld6gzz6zv48zy6xp4n9xu5uqrwvx9km54qaqkkxn72
460c25e6…065c -- 137d [parent] | reply [1 reply]Amethyst does group chat too
jb55 -- 137d [parent] | reply [1 reply]Issue that nostr:npub1fgz3pungsr2quse0fpjuk4c5m8fuyqx2d6a3ddqc4ek92h6hf9ns0mjeck is running into: > another thing I find broken with chatroom is you can't have multiple chats with the same set of people, the conversations would simply combine
460c25e6…065c -- 137d [parent] | reply [1 reply]Yep, that's by design
jb55 -- 137d [parent] | reply [1 reply]we'll support it but feels like a bad design, whats the use case ?
460c25e6…065c -- 137d [parent] | reply [1 reply]To keep it simple. Topic-based approach has way too many edge cases that needs to be dealt with.
460c25e6…065c -- 137d [parent] | reply [1 reply]The issue is to avoid grouping things with the same subject that are not supposed to be grouped, like 2 "Dinner" conversations with different people OR one year apart from each other. You might need a NIP-22-like root event kind to set the topic and then people cite it to group.