# Communities

For more information about communities, read [this document](https://gitlab.syncad.com/hive/hivemind/-/blob/master/docs/communities.md).

All blockchain operations reference communities by their owner account name, i.e. something like `hive-NNNNNN` where NNNNNN represents the community identifier. That'snot really user-friendly.

Moreover, if you want to get communities related information, you have to browse all operations in chronological order to know what happened within each community. Add to this that the community management operations are non-consensual, and therefore not validated by the blockchain. This will put you in front of **a lot of ill-formatted operations** you have to deal with and filter.

That's why HiveSQL communities table stores a real-time updated list of all communities and their properties.

#### Columns

| Name        | Description                                                                                           |
| ----------- | ----------------------------------------------------------------------------------------------------- |
| name        | community account                                                                                     |
| type        | 1=topic 2=journal 3=council                                                                           |
| title       | display name of this community                                                                        |
| about       | short blurb about this community                                                                      |
| description | a blob of markdown to describe the purpose of the community, enumerate rules, etc. (up to 5000 chars) |
| flag\_text  | custom text for reporting content                                                                     |
| language    | primary language                                                                                      |
| nsfw        | true if this community is 18+. UI to automatically tag all posts/comments NSFW                        |


---

# Agent Instructions: 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:

```
GET https://docs.hivesql.io/technical-informations/state-tables/communities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.