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

Misc clarity for 3rd party appservice protocols/locations

Browse source
This commit is contained in:
Travis Ralston 2018-08-27 17:41:52 -06:00
parent 32ac81c588
commit 54032964fc
1 changed files with 7 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

13
specification/application_service_api.rst
View file

@ -184,13 +184,14 @@ Third party networks
++++++++++++++++++++
Application services may declare which protocols they support via their registration
file. These networks are generally for third party services such as IRC that the
application service is managing. Application services may populate a Matrix room
directory for their registered protocols, as defined in the Client-Server API Extensions.
configuration for the homeserver. These networks are generally for third party services
such as IRC that the application service is managing. Application services may populate
a Matrix room directory for their registered protocols, as defined in the Client-Server
API Extensions.
Each protocol may have several "locations". A location within a protocol is a place
in the third party network, such as an IRC channel. Users of the third party network
may also be represented by the application service.
Each protocol may have several "locations" (also known as "third party locations" or "3PLs").
A location within a protocol is a place in the third party network, such as an IRC channel.
Users of the third party network may also be represented by the application service.
Locations and users can be searched by fields defined by the application service, such
as by display name or other attribute. When clients request the homeserver to search