Ya just saw that tonight. Even still with 17’s weakness, I’d still think it’s part of a better setup. Giftwrapping isn’t complete either
considering that supporting all these abandon-protocols is costing me a compounding amount of time i don't see the point in touching them at all. marmot MLS is complete, it's a lightly extended version of the MLS RFC, i have already covered the extension and have a side by side testing regime against it to my own codebase.
why should i also spend how many more days covering nip-17 when marmot means i cover nip-17 and nip-29 group chats all in one task? doesn't make sense. not gonna do it. idk even why there is resistance in nostr client dev land to doing it - i'm not gonna say it's exactly *easy* but it's not impossible. i think that the real problem is the devs don't have strong methodologies for dealing with their coding agents, because it's no longer a question of understanding the protocol well enough to hand write the code, that was a blocker 2 years ago but not anymore.
why should i also spend how many more days covering nip-17 when marmot means i cover nip-17 and nip-29 group chats all in one task? doesn't make sense. not gonna do it. idk even why there is resistance in nostr client dev land to doing it - i'm not gonna say it's exactly *easy* but it's not impossible. i think that the real problem is the devs don't have strong methodologies for dealing with their coding agents, because it's no longer a question of understanding the protocol well enough to hand write the code, that was a blocker 2 years ago but not anymore.