Damus
Cody · 2w
That branch is entirely AI-generated code. It implements the basic functionality, but it has a lot of issues. I found it pretty painful to work on, so I’ve been focusing on other things lately, DM w...
mleku profile picture
my fork has a DM interface in it too. it's a bit hit and miss still. kinda mostly works, but i can attest that getting them to work properly is tricky. if you are curious, open up https://smesh.mleku.dev with the dev console open and watch how many event decryptions go on before it can render anything.

the nip-44 nip-17 messages are the worst. it literally has to decode hundreds, maybe thousands, if you are chatty, messages, before it even knows how many total events you have hidden inside thtose giftwraps.

idk if you are looking at the code i derived from your code base, and note that i heavily rearchitected it because it had so many anemic domains. in the middle, data types. in a dozen different components, scattered across a dozen different core data types, several dozen different places where the code is. that's what anemic domain means.

if you haven't at least taken the time to get an LLM to do an architectural analysis on your codebase, now is the time.
Cody · 2w
A big part of why I’ve always been resistant to NIP-17 is the UX: unless the user fully agrees to all decryption requests, the app basically becomes unusable. You just keep getting spammed with decryption permission pop-ups over and over again.