Skip to content

Conversation

@mchenani
Copy link
Contributor

@mchenani mchenani commented Nov 13, 2025

Add DeleteMessage content type to proto schema to support delete-message payloads in delete_message.proto

Introduce a DeleteMessage protobuf with string message_id = 1; and set content type metadata (authority_id xmtp.org, type_id deleteMessage, version 1.0), plus Go/Java package options.

📍Where to Start

Start with the DeleteMessage message definition and file-level options in delete_message.proto.


Macroscope summarized b4b52c9.

@mchenani mchenani requested a review from a team as a code owner November 13, 2025 16:29
// DeleteMessage message type
message DeleteMessage {
// ID of the message to delete
string message_id = 1;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I know that the platform SDKs typically treat message IDs as strings, we should think about whether we want to internally represent as bytes internally. One less encode/decode step and one less thing to validate (no possibility for encoding errors).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we have the message_id everywhere - kinda e.g. in the ReactionV2, as string, I wanted to be consistent, but will update it.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, that's fair. We probably made a mistake initially having it as a string in the other content types. But I'm fine with erring on the side of consistency.

@mchenani mchenani requested a review from neekolas November 20, 2025 18:36
@mchenani mchenani merged commit b4e7239 into main Nov 20, 2025
7 checks passed
@mchenani mchenani deleted the mc/delete-message branch November 20, 2025 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants