amber was making invalid sigs on the inside of the giftwraps sometimes, but not always
It's usually a matter of some clients only supporting NIP-04, which all clients should have burned on the trash-heap by now, and other clients rightly defaulting to NIP-17.
Though, to be fair, I believe nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgkwaehxw309a3x2an09ehx7um5wgcjucm0d5hsvlnggv discovered some clients that have NIP-17 DMs that weren't being received by other clients that also have NIP-17 DMs.
Did you ever get to the bottom of what was going on with that nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgkwaehxw309a3x2an09ehx7um5wgcjucm0d5hsvlnggv?
Discussion
That's bizarre. Unfortunately I don't know if I can blame Coracle's flakiness on Amber. I think for me it's relay selections but my code is bad and hard to fix.
Very interesting. There's got to be something that triggers Amber making an invalid signature. Is nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszymhwden5te0wfjkccte9enrw73wd9hj7qghwaehxw309aek2ctjvd5zumn0wvh8gmmyv9uj7qgnwaehxw309ahkvenrdpskjm3wwp6kytcppemhxue69uhkummn9ekx7mp0qyfhwumn8ghj7am0wsh82arcduhx7mn99uq32amnwvaz7tmjv4kxz7fwdeek2cewv9c8qtcpzemhxue69uhhyetvv9ujumn0wd68ytnwv46z7qpqw4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvsejewgz aware and investigating?
it seems like its fixed now, i havent seen any failures since last update