Event JSON
{
"id": "340c49c8cdd5d607fa331151a17be15cd67ab06ac5cab42312f6625e22bcf5b7",
"pubkey": "c1831fbe2653f76164421d57db6cee38b8cef8ce6771bc65c12f8543de4b39bf",
"created_at": 1736674412,
"kind": 1,
"tags": [
[
"e",
"aee361f3ee1a1d827be0367355605649f5668b47a5a676aa547153fd09543c43",
"",
"root"
],
[
"e",
"3e72e20314f13dbc7378d9489c0a5703c7640f19ce19c891913166fba8582812"
],
[
"e",
"52e91f84430dd2229fcd67d4c5d3400a4498bfed54908c4973c2f9c94998d47d",
"",
"reply"
],
[
"p",
"c1831fbe2653f76164421d57db6cee38b8cef8ce6771bc65c12f8543de4b39bf"
],
[
"p",
"d599eecdd22afcb162ef59270dda542759b6ee414252305f16eac21ef1a09b85"
],
[
"r",
"https://medium.com/@stephen.biston/resolve-cors-errors-once-and-for-all-three-methods-d821c258d025"
]
],
"content": "Believe me, I am no expert; I just hack around to try and discover what combination of things works most effectively *today*...\n\nBut this article says the problem is on the client side:\n\nhttps://medium.com/@stephen.biston/resolve-cors-errors-once-and-for-all-three-methods-d821c258d025",
"sig": "4e5b3af7e4ae0591859603402767bc135535825a2f818a2db31e402a4a4789f16a12181962be9e4eb1e395c3928f908a74cae1cc949e22919e50c67cce7e68d4"
}
