This is exactly my issue with how other clients implement DMs
However I am not opposed to implementing NIP-17 DMs in noStrudel I just haven't had the time to really sit down and work on them
You are missing their point entirely.
It's not that they hate DMs.
It's that DMs are encrypted and there are currently only a few ways of handling decrypting them.
1. Give the client your nsec so it can decrypt anything itself.
2. Use an external signer with "fully trust this app" enabled, so it will automatically approve decrytion requests from that client.
3. Use an external signer without giving it leeway to auto-approve decryption requests, but then you get spammed with potentially hundreds of requests to manually approve, based on how many DMs you have. Not unread DMs... Total DMs.
4. Have DMs turned off in the client by default, but the user can turn them on when they have determined they trust the client enough to allow it to auto-approve decryption requests.
The first two options involve giving a client more trust than you may be ready to give when first trying it out. The third option is incredibly annoying and renders that client virtually unusable.
nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wf6k2tnrdakj7qg6waehxw309ac8junpd45kgtnxd9shg6npvchxxmmd9usc5pxf was thanking nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7208x3z for making the 4th option available in his client.
Discussion
because you don't think they are important, even though they are the backbone of all other social networks