> I'm curious about the goals part you mentioned toward the end there. You mentioned a relay implementation. Curious what that means. 🌱
Me too 😅 It's something I'll have to put some thought into. Off the top of my head though, things I want:
- Invite codes that a user can enter into a client, which then get sent to the appropriate relays to broker admission
- Multiple dynamic levels of membership, similar to Patreon. Some posts should be accessible publicly, some only for members, and only certain people should be able to post.
- Prevention of content leakage for public notes. Similar to how gift wrap works, but with no encryption. So you might have a public note (maybe protected using AUTH), but you don't want it re-published to other relays. So you instead publish it "to" the relay by doing some kind of relay-specific signature. That way, readers have to know where it came from to verify the signature.
- AUTH support, obviously. I think a way for a user to ask to authenticate would be good — that way relays can serve public content to unauthenticated users without asking for their pubkey. Then users can opt into KYC to access subscriber content.
hodlbod /
npub1jl…jynqn
2023-09-28 19:15:41
in reply to nevent1q…8a7r
Author Public Key
npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqnPublished at
2023-09-28 19:15:41Event JSON
{
"id": "fd36396a6faa87ba90b4bb8d11355ff5b3dfcfd9a7f7fd5689b4ce0ae25c2493",
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"created_at": 1695921341,
"kind": 1,
"tags": [
[
"p",
"7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e",
"wss://relay.damus.io",
"cloud fodder"
],
[
"a",
"30023:97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322:where-is-my-coracle-going",
"",
"root"
],
[
"e",
"0c86269e28fc3234dabe898ba0de640743ed433c958b6623bc3fff9e1bbab840",
"wss://relay.damus.io",
"reply"
]
],
"content": "\u003e I'm curious about the goals part you mentioned toward the end there. You mentioned a relay implementation. Curious what that means. 🌱\n\nMe too 😅 It's something I'll have to put some thought into. Off the top of my head though, things I want:\n\n- Invite codes that a user can enter into a client, which then get sent to the appropriate relays to broker admission\n- Multiple dynamic levels of membership, similar to Patreon. Some posts should be accessible publicly, some only for members, and only certain people should be able to post.\n- Prevention of content leakage for public notes. Similar to how gift wrap works, but with no encryption. So you might have a public note (maybe protected using AUTH), but you don't want it re-published to other relays. So you instead publish it \"to\" the relay by doing some kind of relay-specific signature. That way, readers have to know where it came from to verify the signature.\n- AUTH support, obviously. I think a way for a user to ask to authenticate would be good — that way relays can serve public content to unauthenticated users without asking for their pubkey. Then users can opt into KYC to access subscriber content.",
"sig": "8970e4c03926e263d00e949d6d66aee32eec75663a0b812fac178801811c3abd51413c1f1aa6ce2884501ece9e8bb66e6c5d41ee2751c2a57527412a4bcd2c3e"
}