Ah, interesting, I haven't used telegram that much so maybe I don't quite understand why people use it (or that it has these cross group quotes). I had assumed it was more like signal.
I read NIP29 again this morning.. couple things that stand out to me:
1)"Relays are expected to reject any events that contain timeline references to events not found in their own database". - This part is gonna be hard on the relay side, lotta extra stuff to track/query for.. (3 queries per new event, across the relays database). Is the timeline stuff completely necessary or can relays ignore that and just do ACL checks + not allow older events?
2)private vs. public. Calling it private may set an expectation of privacy.. better words to describe the differences between auth (read ACL) vs no auth (write ACL, open for read). Wish I could think of some other words. "public read, read protected"
3)To really get adoption in your group I think you would need a way to create an 'invite code' that has limited time expiry. Like how discord does (maybe how telegram does too?). Otherwise people will make the group open (which leads to more spam) or closed (which leads to more manual approval and people unable to quickly join). With a code, that enables the group to sign people up in waves..
cloud fodder
npub10np…tl5h
2024-07-05 19:26:10
in reply to nevent1q…9j7v
Author Public Key
npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5hPublished at
2024-07-05 19:26:10Event JSON
{
"id": "68544145ed1d2e3e39b0c86351bfc05c969a8c431e672c8d7bd7f413e10e2f77",
"pubkey": "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e",
"created_at": 1720200370,
"kind": 1,
"tags": [
[
"e",
"0348a66ff5586842df16ffa97e03864c1d5f95f05325f4673680ecdd645ae32a",
"",
"root"
],
[
"e",
"5ef99e59df6dc4b89284bb8b026f268fdf9038c0308b424de49f601a5a8403c0"
],
[
"e",
"dcee5b2c08d8f26996b9053fde6939199a426faeaf4772bf7e103b0ccf7539b8",
"",
"reply"
],
[
"p",
"7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
],
[
"p",
"c5cfda98d01f152b3493d995eed4cdb4d9e55a973925f6f9ea24769a5a21e778"
],
[
"p",
"50809a53fef95904513a840d4082a92b45cd5f1b9e436d9d2b92a89ce091f164"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
]
],
"content": "Ah, interesting, I haven't used telegram that much so maybe I don't quite understand why people use it (or that it has these cross group quotes). I had assumed it was more like signal.\n\nI read NIP29 again this morning.. couple things that stand out to me:\n\n1)\"Relays are expected to reject any events that contain timeline references to events not found in their own database\". - This part is gonna be hard on the relay side, lotta extra stuff to track/query for.. (3 queries per new event, across the relays database). Is the timeline stuff completely necessary or can relays ignore that and just do ACL checks + not allow older events?\n\n2)private vs. public. Calling it private may set an expectation of privacy.. better words to describe the differences between auth (read ACL) vs no auth (write ACL, open for read). Wish I could think of some other words. \"public read, read protected\"\n\n3)To really get adoption in your group I think you would need a way to create an 'invite code' that has limited time expiry. Like how discord does (maybe how telegram does too?). Otherwise people will make the group open (which leads to more spam) or closed (which leads to more manual approval and people unable to quickly join). With a code, that enables the group to sign people up in waves..\n\n\n\n\n\n",
"sig": "5575bfd7ee3fce6be85d4cfdb158f77b1d58a8092534e11696efc4a3cbac76b377ec53a7e09d9bee4cbed7a744af369a1fec7eacef22fef6605f66ea8256275c"
}