Communities

For more information about communities, read this document.

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