Remove RST alert directives, replace with simple Markdown formatting
This commit is contained in:
parent
00c6a866e2
commit
c7cf90abfa
11 changed files with 68 additions and 70 deletions
|
@ -96,11 +96,11 @@ paths:
|
|||
This endpoint is deprecated in favour of the more specific ``/3pid/add``
|
||||
and ``/3pid/bind`` endpoints.
|
||||
|
||||
.. Note::
|
||||
Previously this endpoint supported a ``bind`` parameter. This parameter
|
||||
has been removed, making this endpoint behave as though it was ``false``.
|
||||
This results in this endpoint being an equivalent to ``/3pid/bind`` rather
|
||||
than dual-purpose.
|
||||
**Note:**
|
||||
Previously this endpoint supported a ``bind`` parameter. This parameter
|
||||
has been removed, making this endpoint behave as though it was ``false``.
|
||||
This results in this endpoint being an equivalent to ``/3pid/bind`` rather
|
||||
than dual-purpose.
|
||||
operationId: post3PIDs
|
||||
deprecated: true
|
||||
security:
|
||||
|
|
|
@ -347,11 +347,11 @@ paths:
|
|||
Get information about a URL for the client. Typically this is called when a
|
||||
client sees a URL in a message and wants to render a preview for the user.
|
||||
|
||||
.. Note::
|
||||
Clients should consider avoiding this endpoint for URLs posted in encrypted
|
||||
rooms. Encrypted rooms often contain more sensitive information the users
|
||||
do not want to share with the homeserver, and this can mean that the URLs
|
||||
being shared should also not be shared with the homeserver.
|
||||
**Note:**
|
||||
Clients should consider avoiding this endpoint for URLs posted in encrypted
|
||||
rooms. Encrypted rooms often contain more sensitive information the users
|
||||
do not want to share with the homeserver, and this can mean that the URLs
|
||||
being shared should also not be shared with the homeserver.
|
||||
|
||||
operationId: getUrlPreview
|
||||
produces: ["application/json"]
|
||||
|
|
|
@ -132,12 +132,12 @@ paths:
|
|||
Servers may choose to implement additional access control checks here, for instance that
|
||||
room aliases can only be deleted by their creator or a server administrator.
|
||||
|
||||
.. Note::
|
||||
Servers may choose to update the ``alt_aliases`` for the ``m.room.canonical_alias``
|
||||
state event in the room when an alias is removed. Servers which choose to update the
|
||||
canonical alias event are recommended to, in addition to their other relevant permission
|
||||
checks, delete the alias and return a successful response even if the user does not
|
||||
have permission to update the ``m.room.canonical_alias`` event.
|
||||
**Note:**
|
||||
Servers may choose to update the ``alt_aliases`` for the ``m.room.canonical_alias``
|
||||
state event in the room when an alias is removed. Servers which choose to update the
|
||||
canonical alias event are recommended to, in addition to their other relevant permission
|
||||
checks, delete the alias and return a successful response even if the user does not
|
||||
have permission to update the ``m.room.canonical_alias`` event.
|
||||
|
||||
operationId: deleteRoomAlias
|
||||
security:
|
||||
|
@ -184,10 +184,10 @@ paths:
|
|||
such as allowing server administrators to view aliases regardless of
|
||||
membership.
|
||||
|
||||
.. Note::
|
||||
Clients are recommended not to display this list of aliases prominently
|
||||
as they are not curated, unlike those listed in the ``m.room.canonical_alias``
|
||||
state event.
|
||||
**Note:**
|
||||
Clients are recommended not to display this list of aliases prominently
|
||||
as they are not curated, unlike those listed in the ``m.room.canonical_alias``
|
||||
state event.
|
||||
|
||||
operationId: getLocalAliases
|
||||
security:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue