|
| 1 | +# Buzz domain language |
| 2 | + |
| 3 | +Shared terminology for Buzz product behavior. This glossary currently covers mobile [push suppression](#push-suppression); it is not a complete model of Buzz. |
| 4 | + |
| 5 | +## Notifications |
| 6 | + |
| 7 | +### Mobile push notification |
| 8 | + |
| 9 | +A notification directed to a user's mobile installation through the platform's push service. |
| 10 | + |
| 11 | +### Push suppression |
| 12 | + |
| 13 | +Withholding an otherwise eligible [mobile push notification](#mobile-push-notification) based on [desktop activity](#desktop-activity) and a working connection to the relevant community. It does not depend on whether desktop alerts can be shown. |
| 14 | + |
| 15 | +_Avoid_: Read receipt, mark as read, mute |
| 16 | + |
| 17 | +### Desktop activity |
| 18 | + |
| 19 | +User interaction with the computer running Buzz, including interaction with another application. It is the interaction itself, not a state that lasts afterward, and does not imply that a particular Buzz message was displayed or read. |
| 20 | + |
| 21 | +_Avoid_: Message visibility, read activity |
| 22 | + |
| 23 | +### In-app activity |
| 24 | + |
| 25 | +User interaction inside Buzz. Recent in-app activity remains evidence of [desktop activity](#desktop-activity) after Buzz loses focus; current window focus is a separate condition. |
| 26 | + |
| 27 | +### Desktop inactivity |
| 28 | + |
| 29 | +The state reached when the duration specified in the spec has elapsed since the last observed [desktop activity](#desktop-activity). |
| 30 | + |
| 31 | +### Additional notification delay |
| 32 | + |
| 33 | +A waiting period after [desktop inactivity](#desktop-inactivity) begins before [mobile push notifications](#mobile-push-notification) resume. This is distinct from the inactivity threshold itself. |
| 34 | + |
| 35 | +### Suppressed message |
| 36 | + |
| 37 | +A message whose otherwise eligible [mobile push notification](#mobile-push-notification) was withheld. The term refers to its notification, not withholding the message itself, and says nothing about whether the message has been read. |
| 38 | + |
| 39 | +### Suppression activity signal |
| 40 | + |
| 41 | +Information communicated for deciding whether [desktop activity](#desktop-activity) warrants [push suppression](#push-suppression). It is distinct from [visible presence](#visible-presence) and is not a read receipt. |
| 42 | + |
| 43 | +### Visible presence |
| 44 | + |
| 45 | +The availability status shown to other members, such as online, away, or offline. A chosen visible presence status does not necessarily reflect actual [desktop activity](#desktop-activity). |
| 46 | + |
| 47 | +### Suppression renewal |
| 48 | + |
| 49 | +A [suppression activity signal](#suppression-activity-signal) that extends how long [push suppression](#push-suppression) applies based on activity on one desktop. |
| 50 | + |
| 51 | +### Inactivity cutoff |
| 52 | + |
| 53 | +The time of the last observed [desktop activity](#desktop-activity) plus the duration specified in the spec, when [desktop inactivity](#desktop-inactivity) begins. New desktop activity moves this cutoff forward. |
0 commit comments