Event JSON
{
"id": "b36a4a1bf692b24b679665aae8c4a0bd3959ce217a71f752416a502bac0dd456",
"pubkey": "ed98dd172c8fec81e65ac4d2b0687fe3ac855a12e939c028820df32002c896e7",
"created_at": 1730733082,
"kind": 1,
"tags": [
[
"p",
"4c67f1ec329775408b6cfe504fabdf7915b7bfd39e0cb5b5c09b4799764c68bb",
"wss://relay.mostr.pub"
],
[
"p",
"0729a09d4e0bf980f3d2b3b0c62d2dc79d8df01668c0c106ceff8e36dad8b730",
"wss://relay.mostr.pub"
],
[
"p",
"a1a4eb540235341a2db0d8a08cfb74edc4bb06b316c7bb39580c55559ce71ba1",
"wss://relay.mostr.pub"
],
[
"p",
"55a8695b9cf3190d9ce185047c3f8d26967b811731996cd0a62ee8762f5c96cf",
"wss://relay.mostr.pub"
],
[
"e",
"6a2dab1d49f0a6f3c78f0491095200f67b7af445b55f888f32eef3ab05f9ad81",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://infosec.exchange/users/david_chisnall/statuses/113425323314853456",
"activitypub"
]
],
"content": "nostr:npub1f3nlrmpjja65pzmvlegyl27l0y2m007nncxttdwqndrejajvdzas2me887 nostr:npub1qu56p82wp0ucpu7jkwcvvtfdc7wcmuqkdrqvzpkwl78rdkkckucqswqel2 I think the problem for this specific case is that it's the algorithm that matters, not any of the surrounding code. Anything that's doing the same sequence of operations may leak the details. Anything that's changed may break things like known-bits analysis and not trigger the bug.",
"sig": "128b3c78aa93dcd862084a1be412002eb746a27b6964a4e6a4ea7138298b6f1dbcf99c7ff2af2f0439330186f912c04add5a539bcc5e7d71976d77128262114d"
}