I will reply here everyday until this is done. @jb55 @miljan @jack
It will take all of you less than a day. Put down the new features for a sec, please 🙏, and get basic functionality working so we can retain the current set of users.
My excuse is that damus is preserving the old threads that used deprecated nip10, if people forget about that then many old threads will be broken. Maybe it doesn’t matter though.
@tyiu does your nip-10 approach for damus work, and does it break old threads?
My fix on Primal and what needs to be fixed on Damus are two different things.
You can support reading old threads while support writing new replies using the new recommended part of the NIP-10 spec.
I looked briefly into implementing it in Damus a while back but it seemed like it was a non-trivial refactor requiring a lot of changes so I ended up not doing it.
@jb55 best of both worlds? But the extra work of supporting both might be a pain. I hope for a unified future. Past threads be damned, but if you can keep them that’s cool too.
Old threads are getting nuked from relay wipes either way. It’s worth giving up the fragmented past for a unified future. ✊
Most people aren’t going to switch apps when one is glitching, they’re just going to stop using Nostr altogether & end up calling it glitchy.
Compatibility is key for user retention… for both of you.
GitNestr and Primal are both moving to the new NIP-10 standard and I want all that new user activity to be visible on Damus. I don’t want Damus to be left behind. Let’s stick together. 💜
I just finished this, just writing some tests and will be on testflight soon
💜
Love it. Thank you, Will! 🍻
Now it’s up to Primal to implement that patch. Looking forward to the day when every reply from Primal users no longer show up as quotes on other clients.
Oddbean new post about login | logout 