deploy: 1433b5d5b6
This commit is contained in:
parent
92f8c2fd11
commit
0f808218da
|
@ -176,6 +176,7 @@ for a server admin: see <a href="../usage/administration/admin_api">Admin API</a
|
|||
"is_guest": 0,
|
||||
"admin": 0,
|
||||
"deactivated": 0,
|
||||
"erased": false,
|
||||
"shadow_banned": 0,
|
||||
"creation_ts": 1560432506,
|
||||
"appservice_id": null,
|
||||
|
@ -296,6 +297,7 @@ By default, the response is ordered by ascending user ID.</p>
|
|||
"admin": 0,
|
||||
"user_type": null,
|
||||
"deactivated": 0,
|
||||
"erased": false,
|
||||
"shadow_banned": 0,
|
||||
"displayname": "<User One>",
|
||||
"avatar_url": null,
|
||||
|
@ -306,6 +308,7 @@ By default, the response is ordered by ascending user ID.</p>
|
|||
"admin": 1,
|
||||
"user_type": null,
|
||||
"deactivated": 0,
|
||||
"erased": false,
|
||||
"shadow_banned": 0,
|
||||
"displayname": "<User Two>",
|
||||
"avatar_url": "<avatar_url>",
|
||||
|
@ -387,6 +390,7 @@ User objects contain the following fields:</p>
|
|||
<li><code>user_type</code> - string - Type of the user. Normal users are type <code>None</code>.
|
||||
This allows user type specific behaviour. There are also types <code>support</code> and <code>bot</code>. </li>
|
||||
<li><code>deactivated</code> - bool - Status if that user has been marked as deactivated.</li>
|
||||
<li><code>erased</code> - bool - Status if that user has been marked as erased.</li>
|
||||
<li><code>shadow_banned</code> - bool - Status if that user has been marked as shadow banned.</li>
|
||||
<li><code>displayname</code> - string - The user's display name if they have set one.</li>
|
||||
<li><code>avatar_url</code> - string - The user's avatar URL if they have set one.</li>
|
||||
|
|
|
@ -12474,6 +12474,7 @@ for a server admin: see <a href="admin_api/../usage/administration/admin_api">Ad
|
|||
"is_guest": 0,
|
||||
"admin": 0,
|
||||
"deactivated": 0,
|
||||
"erased": false,
|
||||
"shadow_banned": 0,
|
||||
"creation_ts": 1560432506,
|
||||
"appservice_id": null,
|
||||
|
@ -12594,6 +12595,7 @@ By default, the response is ordered by ascending user ID.</p>
|
|||
"admin": 0,
|
||||
"user_type": null,
|
||||
"deactivated": 0,
|
||||
"erased": false,
|
||||
"shadow_banned": 0,
|
||||
"displayname": "<User One>",
|
||||
"avatar_url": null,
|
||||
|
@ -12604,6 +12606,7 @@ By default, the response is ordered by ascending user ID.</p>
|
|||
"admin": 1,
|
||||
"user_type": null,
|
||||
"deactivated": 0,
|
||||
"erased": false,
|
||||
"shadow_banned": 0,
|
||||
"displayname": "<User Two>",
|
||||
"avatar_url": "<avatar_url>",
|
||||
|
@ -12685,6 +12688,7 @@ User objects contain the following fields:</p>
|
|||
<li><code>user_type</code> - string - Type of the user. Normal users are type <code>None</code>.
|
||||
This allows user type specific behaviour. There are also types <code>support</code> and <code>bot</code>. </li>
|
||||
<li><code>deactivated</code> - bool - Status if that user has been marked as deactivated.</li>
|
||||
<li><code>erased</code> - bool - Status if that user has been marked as erased.</li>
|
||||
<li><code>shadow_banned</code> - bool - Status if that user has been marked as shadow banned.</li>
|
||||
<li><code>displayname</code> - string - The user's display name if they have set one.</li>
|
||||
<li><code>avatar_url</code> - string - The user's avatar URL if they have set one.</li>
|
||||
|
|
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
Loading…
Reference in New Issue