Oddbean new post about login | logout Same relays on Primal and Damus, yet replies made with one client often don’t show in another. 🤔
I have the same issue with Amethyst and Primal.
@Vitor Pamplona how does Amethyst handle NIP-10 & replies in relation to Primal? cc @miljan @tyiu
I believe primal uses their cache, we just connect straight to the kind 3 relays. Either way, there are so many ways to find events that I would never expect to have the same view in any 2 clients.
@elsat
@shawn There is a pending NIP-10 update to make primal backwards compatible with damus thanks to @tyiu Fix is epnding @miljan team update.
Thanks, guys. I’m curious: is this a spec thing or an implementation thing?
It was a bug in the implementation of Primal iOS not respecting the old spec, and also an issue of Damus not catching up to the new (not so new anymore) NIP-10 spec.
Nice, happy other people are noticing this and pushing for a solution.
Is there any more progress on this? It’s ridiculous people are adding new features when Primal replies on Damus still show up as quotes. Can we fix this please? It’d take a day at most. @jb55 @miljan
Yeah its my fault since ive been focused on android dev and haven’t been fixing these edge cases :(
I’m building the GitNeste client and am trying to follow the correct standard. So which is it? Please fix this soon so I can be compatible with both of you.
damus has the old reply approach, and needs to update. see @tyiu patch that makes primal backwards compatible. having the up to date nip-10 + backwards compatibility is the correct approach #nostrability
Where is his patch? Shouldn’t this all be in the NIP repo? We can’t expect people to build backwards-compatible clients if they have to dig like this for something as basic as replies lol.
Ahh are you saying this patch is only for Primal? Does Primal still need to implement this patch? And Damus still needs to implement NIP-10? Is that that correct? @elsat
see nostr:note1f64ngt2pue70r9c8yxv6uph7llw9fxhay2s90vdyernv7smcdmcquzf9yr patch is for primal, correct. @miljan can confirm if merge has occured. damus still needs to implement nip-10, correct. see https://github.com/damus-io/damus/issues/2145
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.
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
see https://github.com/nostrability/nostrability/issues/9 for all I know #nostrability is the sole real world compatibility knowledge base.
GitNestlé ☕