Event JSON
{
"id": "5fcd79baac80dc99061fd0d46384f1acf86592fa12492834e32a74b0c82ccfda",
"pubkey": "d8881295f6442dc93481f888ddb5e74aeaaddac9457e2fb7bd09e68f4d5c8db7",
"created_at": 1716004369,
"kind": 1,
"tags": [
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"",
"mention"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"",
"mention"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"",
"mention"
],
[
"p",
"1739d937dc8c0c7370aa27585938c119e25c41f6c441a5d34c6d38503e3136ef",
"",
"mention"
]
],
"content": "https://gluegroups.com/blog/introducing-glue-work-chat-for-the-ai-era\nThis is very interesting. \n\nTLDR: slack competitor which set threads as the atomic unit instead of channels, similar to ChatGPT. \n\nMaybe we can bring it to nostr once we get other chat features more figured out. Public conversations are already mostly thread-based (twitter conversation model). Private chats (two people or a multiple people) which are thread-based is interesting path to pursue. \n\nnostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc \n\n\nhttps://m.primal.net/IHrD.jpg",
"sig": "bceefd2047411b177832948f20830f8c213d761aca48ee2f297d71517cb031c485b43a1a35e08fd119202d93eb91788442f51a61c5f2daedb7f9921065fc5a11"
}