matrix-spec/data/event-schemas/schema/m.room.message.feedback.yaml

---
allOf:
  - $ref: core-event-schema/room_event.yaml
description: '**NB: Usage of this event is discouraged in favour of the** [receipts module](/client-server-api/#receipts). **Most clients will not recognise this event.** Feedback events are events sent to acknowledge a message in some way. There are two supported acknowledgements: `delivered` (sent when the event has been received) and `read` (sent when the event has been observed by the end-user). The `target_event_id` should reference the `m.room.message` event being acknowledged.'
properties:
  content:
    properties:
      target_event_id:
        description: The event that this feedback is related to.
        type: string
      type:
        description: The type of feedback.
        enum:
          - delivered
          - read
        type: string
    required:
      - type
      - target_event_id
    type: object
  type:
    enum:
      - m.room.message.feedback
    type: string
title: MessageFeedback
type: object
Convert event schemas to yaml We've decided to make the event schemas YAML, so we might as well take advantage of it. (This conversion was done mostly automatically, except for: - s/null/"null"/ in m.room.member - reformat description in m.room.power_levels 9 years ago			`---`
			`allOf:`
			`- $ref: core-event-schema/room_event.yaml`
Fix links in data 4 years ago			description: 'NB: Usage of this event is discouraged in favour of the [receipts module](/client-server-api/#receipts). Most clients will not recognise this event. Feedback events are events sent to acknowledge a message in some way. There are two supported acknowledgements: `delivered` (sent when the event has been received) and `read` (sent when the event has been observed by the end-user). The `target_event_id` should reference the `m.room.message` event being acknowledged.'
Convert event schemas to yaml We've decided to make the event schemas YAML, so we might as well take advantage of it. (This conversion was done mostly automatically, except for: - s/null/"null"/ in m.room.member - reformat description in m.room.power_levels 9 years ago			`properties:`
			`content:`
			`properties:`
			`target_event_id:`
			`description: The event that this feedback is related to.`
			`type: string`
			`type:`
			`description: The type of feedback.`
			`enum:`
			`- delivered`
			`- read`
			`type: string`
			`required:`
			`- type`
			`- target_event_id`
			`type: object`
			`type:`
			`enum:`
			`- m.room.message.feedback`
			`type: string`
			`title: MessageFeedback`
			`type: object`