Event JSON
{
"id": "27fc55ae192ef2a27453a379f658e5240042f3b0a2dcb27261230b643ff2ed77",
"pubkey": "224746be809440211eb69ac598e0fdc60827f26ec091b7a4dc207806cf33b3b8",
"created_at": 1702061065,
"kind": 1,
"tags": [
[
"p",
"2b3df1527af7088dc06aa8e0e2f47994d26bbbb1986d67bc01c9d66a724d5851",
"wss://relay.mostr.pub"
],
[
"p",
"388a5698916c1222cd08c838ff3508914cba87d9a43606a338fd220239621d99",
"wss://relay.mostr.pub"
],
[
"p",
"edd2f0ddf92430e51c09570706a80afe065138598fe84cce658efbbbb50c8b18",
"wss://relay.mostr.pub"
],
[
"p",
"b7fe4910768fb0b39d42bee0b6b2fa60a51a6906bffd0565a144b0b8a6e460b9",
"wss://relay.mostr.pub"
],
[
"p",
"d806b72a5fff07765cf51c2f6d39e7634c8c0152d2f464f65e20084930813531",
"wss://relay.mostr.pub"
],
[
"p",
"ce7f870f472a64eb15f88960d1c8ce551a2d2a89b3992d2bb2007ecfdc3f8093",
"wss://relay.mostr.pub"
],
[
"e",
"870a405247f2acefa8543e532ee6d31e33fff1e15f3c4bd47703a49a0dd7299e",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://podcastindex.social/users/mitch/statuses/111546273974497753",
"activitypub"
]
],
"content": "nostr:npub19v7lz5n67uygmsr24rsw9arejnfxhwa3npkk00qpe8tx5ujdtpgs95al4a nostr:npub18z99dxy3dsfz9nggequ07dggj9xt4p7e5smqdgecl53qywtzrkvscxc3uf nostr:npub1ahf0ph0eyscw28qf2ursd2q2lcr9zwze3l5yenn93mamhdgv3vvqjvjdrc \n\nSecond (lastly), boostagram messages are indeed broken in v4.15.2 🤦♂️\n\nIt turns out there was *always* a race-condition where the boostagram message text could fail to make it into our final boost/keysend request...but this race-condition is exposed and happening 100% of the time due to a async process that was introduced in 4.15.1.\n\nnostr:npub19v7lz5n67uygmsr24rsw9arejnfxhwa3npkk00qpe8tx5ujdtpgs95al4a can you check your NAPSOT? I just sent a refund / bug bounty because I appreciate the timely and critical bug report.",
"sig": "e1ed57dd526f6933560a651e0b11949db27e9f790b6c7d91128d9af7bcb0d699756b6e78c55abb90b66222749f0d4d465f4d471f92897380ca1081486062e7e8"
}