Event JSON
{
"id": "57e94d7059e249ab323673484fa2c4bcfd860bb9044a7294249aa75c46ab71f4",
"pubkey": "16f4abead3eaa4077c5671eacb3b1af158f97ec047b857824e832f5ce37dc539",
"created_at": 1695836096,
"kind": 1,
"tags": [
[
"p",
"81ce934fa6450c6578cb3ca9a4c8b7f854d1317a603bf809803db9ef671e484d",
"wss://relay.mostr.pub"
],
[
"p",
"77fc60b0961a910514f21f6a51f898b5f15ec64f07d144b9518e617e60f02c36",
"wss://relay.mostr.pub"
],
[
"e",
"e5576b4717fb042ead1c447ec1f5cf65b8c29724b18198ea35da0e793bb8dc9a",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://sfba.social/users/somafm/statuses/111138314444323296",
"activitypub"
]
],
"content": "nostr:npub1s88fxnaxg5xx27xt8j56fj9hlp2dzvt6vqalszvq8ku77ec7fpxswkwdqr Yes, it's an annoying issue on Sonos's end. They deployed it wrong (was only supposed to be a limited test deployment)",
"sig": "732f0452b74cd7541c8e57bc042b4f43fe6073bae3c4196c49c9adda26b1e6401bfb4b02d6240affd5c6dded8e86a34976a15f557b20850150193ddc3a6c2950"
}
