The post object
The post object inherits from the Message
object's structure as follows:
Attributes | Description |
---|---|
channel - text | Channel of the message. Ideally, an application would decide and use one channel. |
time - float | Time the post was created in seconds. |
type - text | Text representing the message object type. Value is |
chain** ** - text | The chain used by the sender's account.
Value can be |
sender - text | Chain address who sent and is signing the Post Message. |
- | |
hash_type - optional text | Defaults to sha256. This is the only supported value for now. |
item_content** ** - JSON text | JSON string representing the content of the aggregate. See below for the content of the string. |
item_content.type** ** - text | A string of your choice representing what the post is. Should be simple and lowercase. For instance, for a blog post you could have: a "blog" or a "comment" |
item_content.address** ** - text | Chain address to associate the |
item_content.content** -** object | An object containing the content you want to save. For instance, for a blog post you could have: { body: "This is my content" } |
item_content.content.tags - optional array | If tags were passed in on post create or update you could have: { tags: ["my_first___tag"] } |
item_content.time** ** - float | Time the object was created. |
item_content.ref** ** - text | A text representing a reference. Present if a ref was passed during creation. |
item_hash - hash | The hash of the item_content encrypted with SHA256. |
item_type - optional text |
|
Last updated