Replies and Reposts

A reply is a post with a parent. A repost is a re-share of someone else's post, with an optional quote. Both are signed transactions on the feed shard.

Pipoke runs on Octra Devnet today. Any fee, price, or limit referred to here is a contract setting chosen for testing. Every one is owner-settable, and mainnet values will be different. These docs describe how the mechanics work, not what the numbers are.

#Replies

reply(parent_id, text, attachment, principal) writes a post with kind = reply and parent_id = the global ID of the post you are replying to. The reply lives on your feed shard, not the parent's, because every wallet posts to its own shard. The indexer joins replies to parents by parent_id.

A reply can carry any attachment a top-level post can: image, GIF, video, voice note, link. Voice-note replies and voice-note comments are on chain the same way a voice-note post is. The audio is sealed into your Circle and the reply tx references the oct:// URI.

Replies use the same character cap as the parent tier: free, Premium, or Premium+.

#Reposts

repost(parent_id, quote, principal) re-shares a post on the feed. The quote is optional. If you pass an empty string, the repost stands alone. If you pass text, the repost reads as a quote-repost.

A wallet can repost a given post once. The shard enforces idempotency: a second repost call from the same wallet to the same parent_id reverts. To undo a repost, call unrepost(parent_id, principal).

#Quote reposts

A quote repost is just a repost with a non-empty quote string. The indexer renders the parent as an embed below your quote.

#Threading depth

Pipoke does not cap thread depth. A reply can have a reply can have a reply. The app renders depth visually with indentation up to a small visual cap, then collapses deeper replies into a "view more" button.

#Action fees

Replies and reposts each charge their own action fee in POKE, split 50/40/10 like a top-level post. Voice-note replies cost the same as text replies, regardless of the audio length.

#Voice replies in practice

A typical voice reply flow:

You tap the mic next to the reply box.
The app records up to 30 seconds.
The audio is encrypted with a fresh symmetric key.
The ciphertext is uploaded to your Circle.
The reply tx fires with attachment set to the oct:// URI.
The audience sees the reply in the thread and taps to play.

The audio bytes are on chain. The reply receipt is on chain. The threading is on chain.