Oddbean new post about login | logout 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.
This is a known issue in cross-client compatibility. I think @tyiu came up with a fix.
@node 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 @jb55 @miljan any way you could prioritize these fixes?
Here is the issue on nostrability repo https://github.com/nostrability/nostrability/issues/9
🙏
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: @pavle
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. https://github.com/PrimalHQ/primal-ios-app/pull/124
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 @miljan @Kwinten @bumi
@node 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 @Frogfren17 and @50c5c98c 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.
Which service were you using to send the zap?
I tried to zap you @node it does not go through. I use alby with Amethyst https://image.nostr.build/d1df170e9828ac3a22dfe4512b71ce51094e84ba8d843c8c76ceb1a865d8a146.jpg
Just now?
Yes
That’s odd. I’m on alby as well.
Now it went. Sent you a Q
What’s a Q ?
Quat
17th letter in the alphabet A= 1 B= 2 C= 3 D= 4 ..... Q= 17
