Proposal: Marking resource conversations not intended for human consumption #50
Replies: 2 comments 1 reply
-
@cboscolo What kind of metadata are you looking to store? Is this something we could add into the user preferences? https://github.com/xmtp/proto/blob/main/proto/message_contents/private_preferences.proto Could you give me some examples of the resources you're storing? |
Beta Was this translation helpful? Give feedback.
-
So had a conversation about some potential use cases for this Conversation Nickname: I think this could be solved with our existing user preferences proto code but on a per basis topic id.
Push Notification Preferences: This really depends how granular we are getting here. This feels like a mute or unmute type of flag on a per conversation basis. Which could fit into our existing user preferences like so:
Desired ENS: This feels more like a global setting. And maybe something that they would set per app. Maybe in one app I want to show as my cc @neekolas for thoughts on adding more fields to the user preference proto. |
Beta Was this translation helpful? Give feedback.
-
Proposal: Marking resource conversations not intended for human consumption
Abstract
Marking XMTP conversation as a resource conversation and not intended for humans
Problem
Many proposals are recommending the use of "self" conversations to store meta-data and other information that is intended to be used by XMTP client software for maintaining state and other user preferences. These conversations often contain content formatted as JSON or other machine-readable formats that are not intended for human consumption. We need to mark these conversations as "not intended for humans" so the software can hide them from the UI and Notification services can ignore updates on these conversations.
Proposed Solution
Marking resource conversations
To signify that a conversation is a resource conversation and not intended for end-user human consumption, add an entry to the
conversation.context.metadata
with key ofresource
and any truthy for the value. The actual value of the resource entry can be application specific, or a separate proposal could specify a set of values that multiple clients could share. This proposal seeks only to establish that if the value is set, it is intended to be marked as a resource conversation.Example:
Identifying resource conversations
Applications that are processing conversations should look for metadata with a key of
resource
and if found, treat this conversation as a resource conversation not intended for human consumption.Beta Was this translation helpful? Give feedback.
All reactions