Mitch Downey :pci: on Nostr: npub19v7lz…5al4a npub18z99d…xc3uf npub1ahf0p…vjdrc Second (lastly), boostagram ...
npub19v7lz5n67uygmsr24rsw9arejnfxhwa3npkk00qpe8tx5ujdtpgs95al4a (npub19v7…al4a) npub18z99dxy3dsfz9nggequ07dggj9xt4p7e5smqdgecl53qywtzrkvscxc3uf (npub18z9…c3uf) npub1ahf0ph0eyscw28qf2ursd2q2lcr9zwze3l5yenn93mamhdgv3vvqjvjdrc (npub1ahf…jdrc)
Second (lastly), boostagram messages are indeed broken in v4.15.2 🤦♂️
It 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.
npub19v7lz5n67uygmsr24rsw9arejnfxhwa3npkk00qpe8tx5ujdtpgs95al4a (npub19v7…al4a) can you check your NAPSOT? I just sent a refund / bug bounty because I appreciate the timely and critical bug report.
Second (lastly), boostagram messages are indeed broken in v4.15.2 🤦♂️
It 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.
npub19v7lz5n67uygmsr24rsw9arejnfxhwa3npkk00qpe8tx5ujdtpgs95al4a (npub19v7…al4a) can you check your NAPSOT? I just sent a refund / bug bounty because I appreciate the timely and critical bug report.