> For the complete documentation index, see [llms.txt](https://docs.v2.like.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v2.like.co/zh/general-guides/community.md).

# 社群

想與社群及更多用戶聯繫分享經驗，有渠道嗎？

[LikeCoin Discord](http://discord.gg/likecoin) 歡迎任何人參與，涵蓋創作、開發、治理、產品討論等各種話題，讓公眾與驗證人及各個持份者進行交流。

## 如何加入 LikeCoin Discord

**步驟一**： 註冊 Discord 帳號並於瀏覽器輸入 <https://discord.gg/likecoin> 邀請連結或在 Discord app 參找 LikeCoin。於登入畫面點「接受邀請」。

<figure><img src="https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2FBhl3wcS9Zx3Q4BzC6mfk%2FDiscord%201.png?alt=media&amp;token=f59ae8f6-7afe-45b1-b726-35b2ae15b9e5" alt=""><figcaption><p>點「接受邀請」</p></figcaption></figure>

**步驟二**：看到「您必須先完成一些步驟才可能開始聯天」點「完成」。

<figure><img src="https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2FNUhkJ1W6p0ji9H13yAPq%2FDiscord%202.png?alt=media&amp;token=23056b3c-f82a-454b-a500-01c41765a92c" alt=""><figcaption><p>點「完成」</p></figcaption></figure>

**步驟三**：閱讀群組規則後點「我已詳閱並同意規則」再點「按受」。

<figure><img src="https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2FfcujCCCqGi3r5mCowZBq%2FDiscord%203.png?alt=media&amp;token=745dd2d4-26ab-4a1d-a6fe-0f8ed2435ac7" alt=""><figcaption><p>點「按受」</p></figcaption></figure>

**步驟四**：到 #👍｜verify 頻道按 ✅ 進行認證。

<figure><img src="https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2FjxBDRGQxdVX1ISNaviwE%2FDiscord%204.png?alt=media&amp;token=8bdcf33b-dad7-49d4-8f15-3bc9e7972758" alt=""><figcaption><p>按 ✅ 進行認證</p></figcaption></figure>

此外亦可在 LikeCoin Discord 使用以下功能：

* [#Community Call](https://docs.v2.like.co/zh/general-guides/community/community-call.md)－參與每月社群治理會議
* [#🎫｜open-a-ticket](https://docs.v2.like.co/zh/general-guides/community/open-a-ticket.md) - 使用 Discord 客服工具私訊管理員
* [#🌊｜faucet-mainnet](https://docs.v2.like.co/zh/general-guides/faucet.md) - 主網水龍頭
* [#💧｜faucet-testnet](https://docs.v2.like.co/zh/general-guides/community/faucet-test.md)－獲取少量 LikeCoin 在 testnet 試用各種功能
* [#🔁｜translate-wallet-prefix](https://docs.v2.like.co/zh/general-guides/community/translate-wallet-prefix.md)－雙向查詢新舊前綴錢包地址
* [LikeCoin Disocrd 錢包](https://docs.v2.like.co/zh/general-guides/community/discord-wallet.md) - 在 Discord 傳送及接收 LikeCoin
* [LIKE this mesage](https://docs.v2.like.co/zh/general-guides/community/like-this-mesage.md) - 在 Discord 「拍手」傳送 5 LIKE 予訊息作者
* [Share to DePub](https://docs.v2.like.co/zh/general-guides/dapp/depub.space/from-likecoin-discord-to-depub.space.md) - 從 LikeCoin Discord 推文到 [depub.space](https://depub.space/)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.v2.like.co/zh/general-guides/community.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
