Replying to a reply of a note in Primal. Then when I look at it in Damus, the reply of the reply is under the original note, instead of being under the reply to the note.
Discussion
This is a known issue in cross-client compatibility. I think nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf came up with a fix.
nostr:npub1rzg96zjavgatsx5ch2vvtq4atatly5rvdwqgjp0utxw45zeznvyqfdkxve what’s the note id for that example?
Here’s one example:
nostr:note1mzvhlh37fe0pdu5gvfjrgrq4uk0x4pqrw0aqhq5n4sr9w9nj9ges3j0s9y
OK yeah, the issue is with both Damus and Primal in regard to NIP-10. Damus doesn’t understand the new way of making replies, and Primal didn’t attempt to preserve backwards compatibility when implementing the new way.
I fixed the backwards compatibility issue in Amethyst two months ago.
https://github.com/vitorpamplona/amethyst/pull/737
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr any way you could prioritize these fixes?
Here is the issue on nostrability repo
🙏
I spent about an hour looking through the Primal iOS code, and the code doesn’t match up with the reported behavior. The code adds a “reply” marker event tag before some “p” tags, but nowhere does it create a “root” marker event tag.
createNostrReplyEvent code: https://github.com/PrimalHQ/primal-ios-app/blob/3b1f2d13f261348ecdc219bc600043509d1d926d/Primal/Common/Nostr/NostrObject%2BExtra.swift#L221-L226
The current App Store version is 1.2.46 but what’s checked into GitHub is 1.2.30. The GitHub repository is 16 builds behind, so the backwards incompatible bug might have been introduced in one of those builds.
App Store: https://apps.apple.com/us/app/primal/id1673134518
GitHub repo version: https://github.com/PrimalHQ/primal-ios-app/blob/3b1f2d13f261348ecdc219bc600043509d1d926d/Primal.xcodeproj/project.pbxproj#L2443
cc: nostr:npub1k6tqlj78cpznd0yc74wy3k0elmj4nql87a3uzfz98tmj3tuzxywsf0dhk6
I submitted a fix for the backwards incompatibility issue in Primal iOS. This should make new replies from Primal iOS display properly in Damus and other clients that are still using deprecated positional tags.
💪
Also couldnt zap some getalby addresses from Primal, while using Primal. And inversely, couldn’t zap primal addresses from getalby, while using Damus. Probably not a new issue. But noticed last week when I tested Primal
Thanks - this is #nostrability territory. Opened a new issue here
https://github.com/nostrability/nostrability/issues/24
cc nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub13sajvl5ak6cpz4ycesl0e5v869r5sey5pt50l9mcy6uas0fqtpmscth4np nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x
nostr:npub1rzg96zjavgatsx5ch2vvtq4atatly5rvdwqgjp0utxw45zeznvyqfdkxve which npub were you zapping, or who was zapping you?
Which note? When approximately did this take place?
While using Primal, I tried to zap nostr:npub19xgymswuxyq4sx58enft9c6algrm72a6lchplm4rjzgklufn9ygq5kcu58 and nostr:npub12rzunrxvx89f78h4df284lzvkjqetljkq0200p62ygwmjevx0j8qhehrv9 and it failed. 6 days ago
The other way around I forget who exactly. But it was someone with a primal address and I was using my getalby address.
From Primal to getalby it was around the same time. Roughly a week ago.
I tried to zap you nostr:npub1rzg96zjavgatsx5ch2vvtq4atatly5rvdwqgjp0utxw45zeznvyqfdkxve it does not go through.
I use alby with Amethyst
