It's not implemented yet. It's being currently designed the ...

mar

npub1c7k2hu076gq62vv9unw9urrt4c4utkce6uatlpq9xhestk8s2xqql8qh4c

hex

512db4d47d15fb6a9b5922da9e1fe8c9e3aa0689e2b6da2e9257ebf13fbd5193

nevent

nevent1qqs9ztd56373t7m2ndvj9k57rl5vnca2q6y79dk696f906l38774rycprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsv0t9t78ldyqd9xxz7fhz7p346u279mvvaww4lsszntuc9mrc9rqqvug5er

Kind-1 (TextNote)

2026-09-07T18:18:51Z

↳ 回复 事件不存在

e52020535c4ad24dd625daed2807f38e1645c924ecd68ba9594d720773e3e9ac...

It's not implemented yet. It's being currently designed the friend request system.

LFL has its own database, so technically we could store the connection relationships there and have LFL ignore replies/interactions from anyone who isn't connected. But I don't really want this to become an LFL-only system.

Ideally there would be a NIP/standard for publishing the connection relationship so other clients and relays could understand it too.

Are you suggesting the user's inbox relay should know who they're connected with and reject unauthorized replies before they're even stored? If so, I'd be interested in how you think that should work. That's the part we're still designing.

For now it's going to be an LFL system only and LFL doesn't have a app yet. I believe the app clients have a lot of power and should be designing this type of system and thinking about it.

原始 JSON

{
  "kind": 1,
  "id": "512db4d47d15fb6a9b5922da9e1fe8c9e3aa0689e2b6da2e9257ebf13fbd5193",
  "pubkey": "c7acabf1fed201a53185e4dc5e0c6bae2bc5db19d73abf840535f305d8f05180",
  "created_at": 1788805131,
  "tags": [
    [
      "e",
      "83a31b9a9dc95500fb6334fc3fe04c5d1ce25a2f8b20da19dbc494f9afabdd73",
      "wss://theforest.nostr1.com/",
      "root",
      "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
    ],
    [
      "e",
      "eb0189a6c8f87f2314303f82538afdc3dda33d972f92f31f782fbfa24fa51168",
      "wss://nostr21.com/",
      "",
      "c7acabf1fed201a53185e4dc5e0c6bae2bc5db19d73abf840535f305d8f05180"
    ],
    [
      "e",
      "e52020535c4ad24dd625daed2807f38e1645c924ecd68ba9594d720773e3e9ac",
      "wss://theforest.nostr1.com/",
      "reply",
      "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
    ],
    [
      "p",
      "c7acabf1fed201a53185e4dc5e0c6bae2bc5db19d73abf840535f305d8f05180",
      "wss://relay.letsfo.com/"
    ],
    [
      "p",
      "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
      "wss://pyramid.fiatjaf.com/"
    ],
    [
      "client",
      "Amethyst"
    ]
  ],
  "content": "It's not implemented yet. It's being currently designed the friend request system.\n\nLFL has its own database, so technically we could store the connection relationships there and have LFL ignore replies/interactions from anyone who isn't connected. But I don't really want this to become an LFL-only system.\n\nIdeally there would be a NIP/standard for publishing the connection relationship so other clients and relays could understand it too.\n\nAre you suggesting the user's inbox relay should know who they're connected with and reject unauthorized replies before they're even stored? If so, I'd be interested in how you think that should work. That's the part we're still designing.\n\nFor now it's going to be an LFL system only and LFL doesn't have a app yet. I believe the app clients have a lot of power and should be designing this type of system and thinking about it.",
  "sig": "f6fa20cf6db74cf198285d8edd7f8f3bcd194752df1d28d27574ca9b85576437e94a78e0873cd1fe2df3acfa9911533ff65f8d4e3bca7b917e2bb4acabacd7de"
}