You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit df56b0d
Browse filesBrowse the repository at this point in the historyBrowse files
fix(desktop): use the reacted-to event's signer for the NIP-25 p tag
The desktop reaction path took its `p` tag from `TimelineMessage.pubkey`,
the *displayed* author that `formatTimelineMessages` resolves — which for a
relay-signed agent message is rewritten from the event's `actor`/first `p`
tag, not the signer. NIP-25's `p` tag is the pubkey of the event being
reacted to (the signer), and every other surface in this PR (SDK, CLI, ACP,
mobile) already uses the raw event author. As written, the same target event
could get different `p` tags depending on which client reacted, and a
delegated actor could be notified while the signer was omitted.
Switch the two desktop timeline handlers to the already-retained
`signerPubkey`. Pulse (`useNoteActions`) keeps `note.pubkey`: a kind:1 social
note is user-signed with no delegation, so its author is the signer.
Signed-off-by: Shani Singh <[email protected]>
0 commit comments