> For the complete documentation index, see [llms.txt](https://docs.kumbaya.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumbaya.xyz/social-features/comments-and-yaps.md).

# Comments and yaps

Every token on Kumbaya has its own comment thread. We call posts in those threads **yaps**. This is where most of the conversation, memeing, and community-building happens.

## Posting a yap

On any token's page, the **Thread** (or **Comments**) tab shows the active conversation. To post:

1. Click the input box at the top of the thread.
2. Type your message. The input is a plain text field, so any **emoji** you can pull from your system's keyboard (⌘⌃Space on macOS, Win+. on Windows) works inline.
3. Optionally **attach media** with the paperclip / attach icon. Supported formats:
   * Images: **JPG**, **PNG**, **WebP**, **GIF**
   * Video: **MP4**, **MOV** (QuickTime)
4. Optionally reply to a specific post by clicking the reply icon on it (or typing `>>postNumber` in your message — see below).
5. Optionally toggle **Anon mode** on the composer (the small Anon-mascot icon) — see [**Anonymous posting**](#anonymous-posting) below.
6. Hit submit. Sign the action in your wallet if prompted.

## Anonymous posting

Each yap can be posted **as Anon** instead of under your profile. Toggle the Anon icon in the composer before submitting; the post will appear with the Kumbaya Anon mascot instead of your avatar and name. The on-chain action still comes from your wallet, but the displayed identity is anonymised at the UI level. The first time you switch on Anon mode, a one-time modal explains how it works.

If you'd rather not see Anon posts at all, the thread has a **hide Anon** toggle that filters them out of your view. Other users still see them; this is a personal display preference, not a moderation action.

## Replying — the `>>postNumber` syntax

Yaps are numbered sequentially per token (post #1, #2, #3 …). You can reference any earlier post by typing `>>` followed by its number — for example `>>14`. The reference renders as a clickable link, and the post you referenced gets a "replied to" indicator.

This 4chan-style threading lets long conversations stay coherent without nesting indefinitely.

## Likes, dislikes, tips

Every yap can be:

* **Liked** — a thumbs-up signal.
* **Disliked** — a thumbs-down signal.
* **Tipped** — sent tip credits. See [**Tipping**](/social-features/tipping.md).

Likes/dislikes affect what gets surfaced as trending; tips go directly to the poster's wallet.

## What gets surfaced

The thread sort defaults to chronological with active replies bumped, but trending mechanisms can pull a particularly liked or tipped yap toward the top of the token's page.

## Etiquette

* Stay on theme with the token's prompt — that's what people are here for.
* Posts with original media tend to attract tips.
* Spam, low-effort replies, and obvious shill posts get downvoted fast.

## Where to next

* [**Tipping →**](/social-features/tipping.md)
* [**Your profile and stats →**](/social-features/profile.md)
* [**Discovering tokens →**](/launchpad/discover.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kumbaya.xyz/social-features/comments-and-yaps.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.