Discuss zap button behavior for reposted tweets in the X browser extension

[coderabbitai]

Requested by @saiy2k as follow-up work from #87.

Summary
Discuss the intended UX and implementation rules for showing a Nostr zap button on reposted/retweeted X posts. Current feedback suggests we should avoid adding the zap button to reposted tweets for now because the interaction model is less clear than for likes.

Why this matters

• Reposted tweets can create ambiguity about who should receive the zap.
• Deferring this decision avoids shipping confusing behavior while the browser extension flow is still being established.
• Capturing the product and technical decision separately keeps Browser extension for injecting Nostr Like buttons on X.com PoC #87 focused.

Affected areas

• Browser extension injection logic in
• Future browser extension UI composition for reaction/zap controls
• Any Nostr event mapping logic introduced for zap support

Discussion points

• Should reposted tweets ever show a zap button?
• If yes, who is the zap target: original author, reposter, or both?
• Should UI placement or labeling differ on reposted content?
• What edge cases exist for quoted posts vs reposts?
• What event data and normalization rules would be required?

Acceptance criteria

• Product/UX decision documented for reposted tweets.
• Clear engineering rules defined for when to render or suppress the zap button.
• Follow-up implementation scope identified if the feature is approved.

Backlinks

• PR: Browser extension for injecting Nostr Like buttons on X.com PoC #87
• Source comment: Browser extension for injecting Nostr Like buttons on X.com PoC #87 (comment)