wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarify how external_url is supposed to work

Browse source 
Fixes https://github.com/matrix-org/matrix-doc/issues/1624
This commit is contained in:
Travis Ralston 2018-08-30 10:49:05 -06:00
parent ab14f33060
commit a48f7b9278
1 changed files with 9 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

17
specification/application_service_api.rst
View file

@ -374,13 +374,14 @@ additional parameters on the ``/publicRooms`` client-server endpoint.
{{appservice_room_directory_cs_http_api}} {{appservice_room_directory_cs_http_api}}
Event fields Referencing messages from a third party network
~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. TODO-TravisR: Fix this section to be a general "3rd party networks" section Application services should include an ``external_url`` in the ``content`` of
events it emits to indicate where the message came from. This typically applies
to application services that bridge other networks into Matrix, such as IRC,
where an HTTP URL may be available to reference.
We recommend that any events that originated from a remote network should Clients should provide users with a way to access the ``external_url`` if it
include an ``external_url`` field in their content to provide a way for Matrix is present. Clients should additionally ensure the URL has a scheme of ``https``
clients to link into the 'native' client from which the event originated. or ``http`` before making use of it.
For instance, this could contain the message-ID for emails/nntp posts, or a link
to a blog comment when bridging blog comment traffic in & out of Matrix.