The \n case makes me wonder if the internal string representation in your language always uses either Windows or Unix line endings (\r\n or \n respectively), and coerces everything coming in to that form. Alternatively, there is a specific character encoding (UTF8 in Java for example) that is always used internally, and you're actually getting a ISO-8859-1 message.
Either way, when you naively feed the bytes from the string into the hashing algorithm, you are subtly changing the message (changing Windows line-endings to Unix, or changing ISO-8859-1 to UTF8).
That would be my guess.
>From: (zerosequioso) at 08/20/22 11:37:46 on wss://relay.zerosequioso.com
>---------------
>Are there any gotchas to hashing messages that contain escape characters in the content? I keep getting the wrong hash according to noscl when content contains things like \n or \"
TrentonZero /
npub1sz…4g279
2022-08-20 18:35:51
in reply to nevent1q…0ywt
Author Public Key
npub1szvxprymkgvxclns7rk4czsz79z50fkpenvfusgcq67ptlvctqws54g279Published at
2022-08-20 18:35:51Event JSON
{
"id": "c82560e3fce6fb7694f7591184691149fe8e0e72cf5280105fc185e976c1bf62",
"pubkey": "8098608c9bb2186c7e70f0ed5c0a02f14547a6c1ccd89e411806bc15fd98581d",
"created_at": 1661020551,
"kind": 1,
"tags": [
[
"e",
"498eb8c22d82018c3e3c71ebff337c2350992237184a6fd112f584b3b06f6102",
"",
"reply"
],
[
"p",
"42a0825e980b9f97943d2501d99c3a3859d4e68cd6028c02afe58f96ba661a9d"
],
[
"client",
"more-speech - 202208171549"
]
],
"content": "The \\n case makes me wonder if the internal string representation in your language always uses either Windows or Unix line endings (\\r\\n or \\n respectively), and coerces everything coming in to that form. Alternatively, there is a specific character encoding (UTF8 in Java for example) that is always used internally, and you're actually getting a ISO-8859-1 message.\n\nEither way, when you naively feed the bytes from the string into the hashing algorithm, you are subtly changing the message (changing Windows line-endings to Unix, or changing ISO-8859-1 to UTF8).\n\nThat would be my guess.\n\n\u003eFrom: (zerosequioso) at 08/20/22 11:37:46 on wss://relay.zerosequioso.com\n\u003e---------------\n\u003eAre there any gotchas to hashing messages that contain escape characters in the content? I keep getting the wrong hash according to noscl when content contains things like \\n or \\\"",
"sig": "3440cd1d10b8732831ade1242dab253c370f7ebb0995669d4407d4c91fbb48e7b7c0428c7eeef3fc91d031e23f7badc722615c5a944e4d303edbc8d9048492ea"
}