Farcaster supports "rich" replies where a target message is actually mentioned. On Comm, we're handling this using markdown.
https://linear.app/comm/issue/ENG-11281/farcaster-replies
Depends on D15376
Differential D15377
[lib] Display a reply Authored by tomek on Sep 18 2025, 4:36 PM. Tags None Referenced Files
Subscribers
Details
Farcaster supports "rich" replies where a target message is actually mentioned. On Comm, we're handling this using markdown. https://linear.app/comm/issue/ENG-11281/farcaster-replies Depends on D15376 Send a message. Reply to it on both Comm and Farcaster. Check how the messages look in both apps.
Diff Detail
Event TimelineComment Actions How do we handle converting in the other direction? Ie. when a user uses the reply function in Comm for a Farcaster thread, we send the reply info correctly to the Farcaster backend. This part seems like it might be a bit harder since I think the Farcaster backend tracks replies based on message IDs instead of just simple Markdown
Comment Actions Currently, we don't create proper replies on Comm. Implementing this is more complicated, because of how we currently create replies - just the markdown. We would need to handle a target message ID... but also, on Comm a user could decide to edit a mentioned message after clicking the reply button. So currently, when we reply on Comm, we will see a markdown message on Farcaster - it is visible on the screens from the summary. Created https://linear.app/comm/issue/ENG-11289/farcaster-create-a-protocol-reply to track the proper solution. | |||||||||||||||||||||||||