yeah, they made a blog something about how they couldn't set...

mleku

npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku

hex

6cb47b0680acb9ec08cce944a1350de030e3be63e402d2eaec01805de757a41a

nevent

nevent1qqsxedrmq6q2ew0vprxwj39px5x7qv8rhe37gqkjatkqrqzauat6gxsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsyeqqz27jc32pgf8gynqtu90d2mxztykj94k0kmttxu37nk3lrktcdc2ej3

Kind-1 (TextNote)

2026-03-24T15:38:46Z

↳ Reply to cloud fodder (npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h)

their argument against auth usually boils down to, they dont want the relay knowing anything. so they'd rather it be wide open to the entire internet...

yeah, they made a blog something about how they couldn't set protected flags because of lack of support in relays (hehe there almost isn't nips for relays that aren't supported in orly) and anyway, you need nip-42 to get protected events because that's the only way to actually check nip-70 tags actually are being enforced.

it's even deeper.

and as claude pointed out to me about this discussion, you either have to have auth or add a restriction created by the group admins that confine the activity to trusted relays. and even then, if they are wide open, the metadata is still wide open without auth.

that's why it's nice to know someone not only has written a Go marmot SDK now, currently finishing up the polish on a radically rewritten smesh client, which only uses marmot.

Raw JSON

{
  "kind": 1,
  "id": "6cb47b0680acb9ec08cce944a1350de030e3be63e402d2eaec01805de757a41a",
  "pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
  "created_at": 1774366726,
  "tags": [
    [
      "e",
      "003ef27fcdaf123483c00682fb48f7c41875fb00e3160b63c2fcc8ae15472bdf",
      "wss://pyramid.fiatjaf.com/",
      "root",
      "efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19"
    ],
    [
      "e",
      "ddab6cd43c33df569863c406dac7717e16284ee854e9ffb40672e0396d50eb20",
      "wss://theforest.nostr1.com/",
      "reply",
      "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
    ],
    [
      "p",
      "efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19"
    ],
    [
      "p",
      "b43102b1aa5d3cb5f525726a8d166597ef029a121d0b45976f21a57841643004"
    ],
    [
      "p",
      "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
    ],
    [
      "client",
      "smesh",
      "https://smesh.mleku.dev"
    ]
  ],
  "content": "yeah, they made a blog something about how they couldn't set protected flags because of lack of support in relays (hehe there almost isn't nips for relays that aren't supported in orly) and anyway, you need nip-42 to get protected events because that's the only way to actually check nip-70 tags actually are being enforced.\n\nit's even deeper.\n\nand as claude pointed out to me about this discussion, you either have to have auth or add a restriction created by the group admins that confine the activity to trusted relays. and even then, if they are wide open, the metadata is still wide open without auth.\n\nthat's why it's nice to know someone not only has written a Go marmot SDK now, currently finishing up the polish on a radically rewritten smesh client, which only uses marmot.",
  "sig": "4a3333040cd3e8d10ddbe1b0adf24565e2f5a12fd9ca795d18a54458bdcef4260148111e706ba36be95505a0613d7ad2ce13dbd01da075069fdde281825d7611"
}