They're using Primal.
Discussion
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr did noStrudel get switched to NIP-17 DMs? I know Primal is still using NIP-04. Or at least, I am relatively sure it is.
Hmm. I just tested sending myself a DM from an account I set up on Primal for testing purposes, and I received it on Nostrudel without issue, BUT it took a while for Nostrudel to load my DMs in general. Also, make sure you have it set to Global if you aren't following the person who is DMing you.
Also confirmed that Nostrudel is still NIP-04 DMs, not NIP-17. None of my NIP-17 conversations show up at all. This means Primal and Nostrudel are both still using the same (outdated and deprecated) standard, so there should be no issues as long as you are reading DMs from relays they are writing to.
DMs are just so badly broken and incompatible. It's just easier to tell people to use 0xchat for nostr DMs and chats.
DMs are also badly broken with nostr users, not knowing how to engage in a private channel. I think I will stick to the policy of not reading or replying to DMs unless absolutely sure of the person.
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?
amber was making invalid sigs on the inside of the giftwraps sometimes, but not always
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
People DM with NIP-17 and never hear from people that only use NIP-04 clients and then end up using other clients or toggling odd NIP-17 to communicate. It's a horrible user experience.
100% agreed. NIP-04 should not be a thing anymore. NIP-17 should be the standard for all DMs on Nostr until we have something better.