I made the report less academic, and more actionable.

elsat

npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5

hex

2bf6211a45e9fd0637d97b3ef7db01641df09a1f4e334ddd4f994762ff6871c9

nevent

nevent1qqszha3prfz7nlgxxlvhk0hhmvqkg80sng05uv6dm48ej3mzla58rjgprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgspw5udc2nzw6wsj3plrrphe0343744h0ucz9e4g248chl3w8kh03qww5fm7

Kind-1 (TextNote)

2026-02-24T16:03:00Z

↳ Reply to elsat (npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5)

Thanks for taking interest. I will add methodology overview to the readme. To your questions: 1. I extracted the algorithms from nostr outbox implemen...

I made the report less academic, and more actionable.

Specific to your question on how to implement the cs algo - mab - see

https://github.com/nostrability/outbox/blob/main/IMPLEMENTATION-GUIDE.md#7-learn-from-what-actually-works

And

https://github.com/nostrability/outbox/blob/main/IMPLEMENTATION-GUIDE.md#improvement-opportunities

MAB complements nip-66 well - nip-66 checks liveness before asking relays, whereas MAB tracks relay health after asking the relay, and scores it.

Nosotros nostr:npub1cesrkrcuelkxyhvupzm48e8hwn4005w0ya5jyvf9kh75mfegqx0q4kt37c looks like has a “seen” table (event created at x seen on relay y), and it is not providing feedback to relay selection for future lookups.

Raw JSON

{
  "kind": 1,
  "id": "2bf6211a45e9fd0637d97b3ef7db01641df09a1f4e334ddd4f994762ff6871c9",
  "pubkey": "17538dc2a62769d09443f18c37cbe358fab5bbf981173542aa7c5ff171ed77c4",
  "created_at": 1771948980,
  "tags": [
    [
      "e",
      "bcb29c08a3efe1c101858d0476b1c6d24690e3438978fd3893d3a0c9fc6224c8",
      "wss://pyramid.fiatjaf.com/inbox",
      "root",
      "17538dc2a62769d09443f18c37cbe358fab5bbf981173542aa7c5ff171ed77c4"
    ],
    [
      "e",
      "a11d74815647fc724e9d9785a005e26b06920a4405c82cbc013f61574a8718bb",
      "wss://pyramid.fiatjaf.com",
      "reply",
      "17538dc2a62769d09443f18c37cbe358fab5bbf981173542aa7c5ff171ed77c4"
    ],
    [
      "p",
      "9ec7a778167afb1d30c4833de9322da0c08ba71a69e1911d5578d3144bb56437"
    ],
    [
      "p",
      "4a0510f26880d40e432f4865cb5714d9d3c200ca6ebb16b418ae6c555f574967"
    ],
    [
      "p",
      "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
    ],
    [
      "p",
      "e771af0b05c8e95fcdf6feb3500544d2fb1ccd384788e9f490bb3ee28e8ed66f"
    ],
    [
      "r",
      "https://github.com/nostrability/outbox/blob/main/IMPLEMENTATION-GUIDE.md#7-learn-from-what-actually-works"
    ],
    [
      "r",
      "https://github.com/nostrability/outbox/blob/main/IMPLEMENTATION-GUIDE.md#improvement-opportunities"
    ],
    [
      "p",
      "c6603b0f1ccfec625d9c08b753e4f774eaf7d1cf2769223125b5fd4da728019e"
    ]
  ],
  "content": "I made the report less academic, and more actionable.\n\nSpecific to your question on how to implement the cs algo - mab - see\n\nhttps://github.com/nostrability/outbox/blob/main/IMPLEMENTATION-GUIDE.md#7-learn-from-what-actually-works\n\nAnd\n\nhttps://github.com/nostrability/outbox/blob/main/IMPLEMENTATION-GUIDE.md#improvement-opportunities\n\nMAB complements nip-66 well - nip-66 checks liveness before asking relays, whereas MAB tracks relay health *after* asking the relay, and scores it.\n\nNosotros nostr:npub1cesrkrcuelkxyhvupzm48e8hwn4005w0ya5jyvf9kh75mfegqx0q4kt37c looks like has a “seen” table (event created at  x seen on relay y), and it is not providing feedback to relay selection for future lookups.",
  "sig": "6fb27d15e8539fce40fc17272c58492307c714657de6f137032fbb42f17d08a9dc7ff20561365be655faaca19c4f2dde79ed8525cdb695e6c95835821e263527"
}