Oddbean new post about login | logout 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