social.colibri.beta.actor.putSpaceModeration
Pushes one of the requesting user's social.colibri.beta.actor.spaceModeration records to the AppView, so it takes effect immediately instead of waiting for a sync notification. The client writes or deletes the record in its own personal space first, then calls this.
Details · procedure
| Kind | procedure |
|---|---|
| Authority | actor.beta.colibri.social |
| Indexed |
Procedure
procedure · POSTInput
application/jsonThe community.
hideModeratedMessages
booleanThe new option for this community. Absent together with remove returns the community to the global option.
remove
booleanRemoves the community's options so it follows the global ones. Ignored when hideModeratedMessages is present.
Output
application/jsonThe requesting user's settings, after the update.
Errors
AuthRequired
The request has no valid service auth.
InvalidRequest
Neither hideModeratedMessages nor remove is present.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Moderation view options for one community, overriding the ones in social.colibri.beta.actor.clientPreferences. The record key is the community's DID. Deleting the record returns the community to the global options.
-
Pushes one of the requesting user's social.colibri.beta.actor.spaceNotification records to the AppView, so it takes effect immediately instead of waiting for a sync notification. The client writes or deletes the record in its own personal space first, then calls this.
-
social.colibri.beta.actor.putSettings
procedurePushes the requesting user's social.colibri.beta.actor.settings record to the AppView, so it takes effect immediately instead of waiting for a sync notification. The client writes the record to its own personal space first, then calls this. An absent field leaves the current value unchanged.
-
social.colibri.beta.actor.putMutes
procedurePushes the requesting user's mute list and list of left threads to the AppView, so they take effect immediately instead of waiting for a sync notification. The client writes the underlying mute records to its own personal space first, then calls this. Each list the request carries replaces the AppView's whole copy of that list.