I find this default behavior in White Noise slightly disturb...

codonaft

npub1alptdev5srcw2hxg03567p4k6xs3lgj7f6545suc0rzp0xw98svse7rg94

hex

003ef27fcdaf123483c00682fb48f7c41875fb00e3160b63c2fcc8ae15472bdf

nevent

nevent1qqsqq0hj0lx67y35s0qqdqhmfrmugxr4lvqwx9stv0p0ej9wz4rjhhcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgswls4kuk2gpu89tny8c6d0q6mdrggl5f0ya226gwv833qhn8zncxged6f2x

Kind-1 (TextNote)

2026-03-24T10:22:16Z

I find this default behavior in White Noise slightly disturbing:

https://github.com/marmot-protocol/whitenoise/issues/528

Not sure why there are not auth-only relays. NIP-42 auth per session doesn't work yet, or/and properly working NIP-42 relays are not really that common yet?

Forward secrecy doesn't really work when NIP-42 is not a requirement for NIP-59 gift wraps: either you or your buddy may expose them with these default relays for example.

Similar issue with the NIP-46 signers: private events exposed in the wild

https://github.com/fiatjaf/nak/issues/116

If you're building a signer, please consider testing/making it compatible with NIP-42 relays and optionally making it show a warning if it's connected over a non-auth relay (or specifically a relay that exposes kind 24133 events).

#devstr #privacy #whitenoise

Raw JSON

{
  "kind": 1,
  "id": "003ef27fcdaf123483c00682fb48f7c41875fb00e3160b63c2fcc8ae15472bdf",
  "pubkey": "efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19",
  "created_at": 1774347736,
  "tags": [
    [
      "L",
      "ISO-639-1"
    ],
    [
      "l",
      "en",
      "ISO-639-1"
    ],
    [
      "t",
      "devstr"
    ],
    [
      "t",
      "privacy"
    ],
    [
      "t",
      "whitenoise"
    ],
    [
      "nonce",
      "17",
      "7"
    ]
  ],
  "content": "I find this default behavior in White Noise slightly disturbing:\n\nhttps://github.com/marmot-protocol/whitenoise/issues/528\n\nNot sure why there are not auth-only relays. NIP-42 auth per session doesn't work yet, or/and properly working NIP-42 relays are not really that common yet?\n\nForward secrecy doesn't really work when NIP-42 is not a requirement for NIP-59 gift wraps: either you or your buddy may expose them with these default relays for example.\n\nSimilar issue with the NIP-46 signers: private events exposed in the wild\n\nhttps://github.com/fiatjaf/nak/issues/116\n\nIf you're building a signer, please consider testing/making it compatible with NIP-42 relays and optionally making it show a warning if it's connected over a non-auth relay (or specifically a relay that exposes kind 24133 events).\n\n#devstr #privacy #whitenoise\n",
  "sig": "f505f96633e7afd937228dcb1cb4ccfa3d0132648ce394e48c7f727b5b71287b1dda13171238b82d4282a96a12e586cab4ac3951e4df2dfc3e34cb5dd83cfb50"
}