Event JSON
{
"id": "4cb5450f5dccb3a74bb3c7ff5df2b700a64b6934c62c2a16d31c0907fab1fe55",
"pubkey": "1d9641cfd78d02e278739e563e1229e843f9ea250b73887c8a186bfae948fbbe",
"created_at": 1732304289,
"kind": 1,
"tags": [
[
"p",
"f374c6a0ce586226a9f40f5daf35d8f7310593b8be55cda581ffa77ede49f9c5",
"wss://relay.mostr.pub"
],
[
"p",
"d9cbb6247465a092d46b6e4f07c0b9c021046b220897db5b90700b16736edcd5",
"wss://relay.mostr.pub"
],
[
"zap",
"1d9641cfd78d02e278739e563e1229e843f9ea250b73887c8a186bfae948fbbe",
"wss://relay.mostr.pub",
"0.915"
],
[
"zap",
"6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9",
"wss://relay.mostr.pub",
"0.085"
],
[
"e",
"e31df9aed5f96bc735be33fa02b317314649731a2b4071f56026cda5cf7d8a91",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://kosmos.social/users/bumi/statuses/113528293921182147",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq7d6vdgxwtp3zd205paw67dwc7ucstyache2umfvpl7nhahjfl8zsk0ayy4 The main problem is that you can not change the node as the key is published in the feed. \nAnd thus it's a bit harder for service providers to do - which is also likely why Strike \u0026 Co. do not offer it (and PC2.0 is just too small for them I guess to care)\n\nBut other solutions have other problems as you mention, that's why we're still on keysend and it's good. \nEspecially for node runners it's good as it does not require anything else.",
"sig": "fab0f052e1238feb6c8462a878c5038893e8fdd88aecc25751ed5ce05721435da0a5df810c9f87ab4f0b34396d401d4a51d09488bb7b0238ffee1cc262b8259e"
}