Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message Content Type #786

Open
cvarjao opened this issue Jun 6, 2023 · 2 comments
Open

Message Content Type #786

cvarjao opened this issue Jun 6, 2023 · 2 comments

Comments

@cvarjao
Copy link

cvarjao commented Jun 6, 2023

Bases on Aries RFC 0095: Basic Message Protocol 1.0, there is no way to to know if a message can contain rich text (e.g.: html, markup).

From an issuer perspective they may want to send message that contains links, and want to annotate those links in a nice hyperlink way.

Workaround:

  • parse URLs based on http:// and http:// and display as hyperlink
@swcurran
Copy link
Member

swcurran commented Jun 6, 2023

The “plan” amongst the early community members was that there would be a “Rich Message Protocol” to compliment the “Basic Message Protocol”. Such a protocol was discussed at Rebooting Web of Trust in Fall 2022 by a group lead by @karimStekelenburg and demonstrated by (I think) @genaris that showed features like link sharing, image sharing, file sharing and so on.

I think the path to this is not to enhance Basic Message, but to define a protocol for advanced chat.

@TimoGlastra
Copy link
Member

Agreed with what Stephen said. The protocol purposely mentions the simplicity as a feature.

@genaris has made custom protocols (and plugins for AFJ) to do read receipts, image sharing, and other rich features.

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

No branches or pull requests

3 participants