Abstract: A database node selects one of a number of database mirror hosts to perform a database read query. In theory, mirror hosts store redundant database entries. In practice, some mirror hosts fail to receive or retain some entries, e.g. if a mirror host was down for maintenance, a mirror host was overburdened, etc. The health of a mirror host, quantified as a health score, represents a likelihood that an insert statement was received and retained. Health scores are generated based on health metrics—data periodically retrieved from mirror hosts used to infer how well the database was operating, e.g. a count of entries that were inserted, a count of errors encountered while the entries were inserted, etc. If the database read query specifies entries inserted during a specific time period, the mirror host may be selected based on the health scores representing that time period.

Abstract: Verification of user identities is an important aspect of computer and network security. In some instances, a first user may attempt to engage with a second user via a web application, mobile phone app, or other software without necessary knowing that the identity of a second user is accurate. The computer security problem of identity verification may be particularly acute when the only contact information is an email address, phone number, or other electronic identifier that can potentially change ownership (e.g. a person may get a new phone number, someone might purchase an Internet domain and thus change ownership of an email address, etc.) This disclosure and claims relate to techniques that allow for enhanced security by verifying an identity of a user via specific prompts and interactions provided via software. Particular credentials may be required in order to verify user identity, including biometrics and other specific required responses.

Abstract: A database node selects one of a number of database mirror hosts to perform a database read query. In theory, mirror hosts store redundant database entries. In practice, some mirror hosts fail to receive or retain some entries, e.g. if a mirror host was down for maintenance, a mirror host was overburdened, etc. The health of a mirror host, quantified as a health score, represents a likelihood that an insert statement was received and retained. Health scores are generated based on health metrics—data periodically retrieved from mirror hosts used to infer how well the database was operating, e.g. a count of entries that were inserted, a count of errors encountered while the entries were inserted, etc. If the database read query specifies entries inserted during a specific time period, the mirror host may be selected based on the health scores representing that time period.

Abstract: A database node selects one of a number of database mirror hosts to perform a database read query. In theory, mirror hosts store redundant database entries. In practice, some mirror hosts fail to receive or retain some entries, e.g. if a mirror host was down for maintenance, a mirror host was overburdened, etc. The health of a mirror host, quantified as a health score, represents a likelihood that an insert statement was received and retained. Health scores are generated based on health metrics—data periodically retrieved from mirror hosts used to infer how well the database was operating, e.g. a count of entries that were inserted, a count of errors encountered while the entries were inserted, etc. If the database read query specifies entries inserted during a specific time period, the mirror host may be selected based on the health scores representing that time period.

Abstract: Verification of user identities is an important aspect of computer and network security. In some instances, a first user may attempt to engage with a second user via a web application, mobile phone app, or other software without necessary knowing that the identity of a second user is accurate. The computer security problem of identity verification may be particularly acute when the only contact information is an email address, phone number, or other electronic identifier that can potentially change ownership (e.g. a person may get a new phone number, someone might purchase an Internet domain and thus change ownership of an email address, etc.) This disclosure and claims relate to techniques that allow for enhanced security by verifying an identity of a user via specific prompts and interactions provided via software. Particular credentials may be required in order to verify user identity, including biometrics and other specific required responses.

Abstract: Methods and systems are provided for sending payments electronically, wherein the user's certainty that the payments are being sent to the correct recipient are substantially enhanced. The user can request information from the recipient to verify the email address or phone number of the recipient. A communication can be sent to the recipient and the communication can request that the recipient send information that verifies the identity of the recipient to the user. For example, the communication can request that the recipient send a picture of the recipient, an audio voice file of the recipient, or a handwriting sample to the user.

Abstract: Methods and systems are provided for sending payments electronically, wherein the user's certainty that the payments are being sent to the correct recipient are substantially enhanced. The user can request information from the recipient to verify the email address or phone number of the recipient. A communication can be sent to the recipient and the communication can request that the recipient send information that verifies the identity of the recipient to the user. For example, the communication can request that the recipient send a picture of the recipient, an audio voice file of the recipient, or a handwriting sample to the user.

Abstract: A system, machine-readable storage medium storing at least one program, and computer-implemented method for routing a notification to at least one device of a user is provided. User preference data including usage data is obtained from a user. The usage data may relate to activity of the user on at least one device and may indicate a preference of the user in receiving notifications on the at least one device. The occurrence of a notification event is detected. In response to the detection of the notification event, a notification is communicated to the user in accordance with the user preference data. The notification may indicate that a notification event has occurred.