app.bivri.actor.getPreferences
Read the authenticated account's own preferences. Scoped to the caller and to nobody else: there is no parameter naming whose preferences to read, because one account's preferences are never another account's business. An account that has never set a preference reads the defaults rather than an absence, so a client has nothing to guess.
Details · query
| Kind | query |
|---|---|
| Authority | actor.bivri.app |
| Indexed |
What's different
same NSID · two revisions from the same publisher3 changes, all backward compatible
Records and requests that were valid against the base schema stay valid against this one.
Query · output
#main
Added
contentFilters
compatibleNew optional property.
ref app.bivri.actor.defs#contentFilterPreferences
Added
mutedTags
compatibleNew optional property.
ref app.bivri.actor.defs#mutedTagPreferences
Added
mutedWords
compatibleNew optional property.
ref app.bivri.actor.defs#mutedWordPreferences
2 properties and 1 error unchanged
Open the full schema diff →