You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use DIDComm to relay messages between different chat agents (Signal, Slack, WhatsaApp, email, SMS). This is a service extension of the general Relay requirement from the DIF DWN specification.
This will effectively allow a user to have messages from e.g. Alice's Whatsapp forwarded to Bob's Slack channel. We foresee that this will be a crucial requirement to enable marketplaces where participants might have differing preferences or capabilities when it comes to communication.
enum ChannelType(agent: URI):
case Slack extends ChannelType(URI("https://slack.com/api/chat.postMessage"))
case WhatsApp extends ChannelType(URI("https://api.whatsapp.com/send"))
case Signal extends ChannelType(URI("https://signal.org/api/v1/send"))
case Telegram extends ChannelType(URI("https://api.telegram.org/bot"))
case Email extends ChannelType(URI("smtp://smtp.gmail.com:587"))
case SMS extends ChannelType(URI("https://api.twilio.com/2010-04)-01/Accounts/ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/Messages.json")))
// did method = did:peer
case class Channels(channel: ChannelType, channelPairwiseDid: String)
Use DIDComm to relay messages between different chat agents (Signal, Slack, WhatsaApp, email, SMS). This is a service extension of the general Relay requirement from the DIF DWN specification.
This will effectively allow a user to have messages from e.g. Alice's Whatsapp forwarded to Bob's Slack channel. We foresee that this will be a crucial requirement to enable marketplaces where participants might have differing preferences or capabilities when it comes to communication.
See: https://identity.foundation/decentralized-web-node/spec/#topology and https://identity.foundation/decentralized-web-node/spec/#addressing
For did:peer implementation see: https://identity.foundation/peer-did-method-spec/
The text was updated successfully, but these errors were encountered: