Abstract: A push notification distribution system centralizes the management and delivery of push notifications to applications executing on electronic devices. Registration requests to register applications for push notifications may be aggregated and sent as an aggregated registration request. The delivery priority of push notifications may be managed according to specified preferences. Upon receiving a push notification intended for an electronic device, a delivery priority of the push notification may be changed if an application identifier associated with the push notification is found on a list of application identifiers with designed delivery priorities.

Abstract: This application sets forth techniques for managing phone number-based user accounts. According to some embodiments, a server computing device can be configured to carry out the steps of (1) receiving, from a first client computing device, a request to create a user account based on a phone number, (2) in response to authenticating that the first client computing device is associated with the phone number: creating the user account based on the phone number, creating a hidden contact address based on the phone number, and assigning the hidden contact address to the user account, and (3) in response to receiving a notification that a second client computing device is associated with the phone number: requiring the user account to be updated to be based on a different phone number, or assigning, to the user account, a visible contact address based on the phone number.

Abstract: A push notification distribution system centralizes the management and delivery of push notifications to applications executing on electronic devices. Registration requests to register applications for push notifications may be aggregated and sent as an aggregated registration request. The delivery priority of push notifications may be managed according to specified preferences. Upon receiving a push notification intended for an electronic device, a delivery priority of the push notification may be changed if an application identifier associated with the push notification is found on a list of application identifiers with designed delivery priorities.

Abstract: This application sets forth techniques for managing phone number-based user accounts. According to some embodiments, a server computing device can be configured to carry out the steps of (1) receiving, from a first client computing device, a request to create a user account based on a phone number, (2) in response to authenticating that the first client computing device is associated with the phone number: creating the user account based on the phone number, creating a hidden contact address based on the phone number, and assigning the hidden contact address to the user account, and (3) in response to receiving a notification that a second client computing device is associated with the phone number: requiring the user account to be updated to be based on a different phone number, or assigning, to the user account, a visible contact address based on the phone number.

Abstract: Implementations of the subject technology provide for performing, by a device, a request for obtaining information related to a phone authentication certificate (PAC) that was generated for the device, the PAC authenticating that a particular phone number is associated with the device, the request including packets of data. The subject technology receives the information related to the PAC, the information including an indication that the PAC was generated for the device. The subject technology sends, from the device, a request for validating the PAC to a remote server based at least in part on the information related to the PAC. Further, the subject technology receives a confirmation of validating the PAC from the remote server based at least in part on the information related to the PAC.

Abstract: This application sets forth techniques for managing phone number-based user accounts. According to some embodiments, a server computing device can be configured to carry out the steps of (1) receiving, from a first client computing device, a request to create a user account based on a phone number, (2) in response to authenticating that the first client computing device is associated with the phone number: creating the user account based on the phone number, creating a hidden contact address based on the phone number, and assigning the hidden contact address to the user account, and (3) in response to receiving a notification that a second client computing device is associated with the phone number: requiring the user account to be updated to be based on a different phone number, or assigning, to the user account, a visible contact address based on the phone number.

Abstract: A push notification distribution system centralizes the management and delivery of push notifications to applications executing on electronic devices. Registration requests to register applications for push notifications may be aggregated and sent as an aggregated registration request. The delivery priority of push notifications may be managed according to specified preferences. Upon receiving a push notification intended for an electronic device, a delivery priority of the push notification may be changed if an application identifier associated with the push notification is found on a list of application identifiers with designed delivery priorities.

Abstract: The subject disclosure provides systems and methods for sender verification for encrypted electronic messaging. The discloses systems and methods may facilitate reducing or preventing spam messages between electronic devices. An electronic device may determine, prior to sending an electronic message to another device with a first level of encryption that is higher than a second level of encryption, whether the electronic device is eligible to send the message with the first level of encryption. If an electronic device determines that it is ineligible to send the message with the first level of encryption to another electronic device, a first message from the electronic device to the other electronic device may be sent with the second level of encryption as part of an unencrypted or low encryption handshake between the devices.

Abstract: Disclosed herein are techniques for enabling a user to activate a new device with a Mobile Network Operator (MNO) without requiring the user to provide MNO authentication credentials that are easily forgotten. The user activates the new device using credentials from an existing device (associated with the user) that is trusted by the MNO and also using a trust score provided by a third-party server that has knowledge of associations between the user and the existing device. The new device can be a supplemental device, such as a wearable device to a cellular phone, where both devices remain capable of accessing services provided by the MNO after the new device is activated with the MNO. The new device can also be a replacement device, such as a new phone, tablet, or wearable device, where the new device supplants access to services provided by the MNO for an existing device.

Abstract: Implementations of the subject technology provide for performing, by a device, a request for obtaining information related to a phone authentication certificate (PAC) that was generated for the device, the PAC authenticating that a particular phone number is associated with the device, the request including packets of data. The subject technology receives the information related to the PAC, the information including an indication that the PAC was generated for the device. The subject technology sends, from the device, a request for validating the PAC to a remote server based at least in part on the information related to the PAC. Further, the subject technology receives a confirmation of validating the PAC from the remote server based at least in part on the information related to the PAC.

Abstract: Disclosed herein are techniques for enabling a user to activate a new device with a Mobile Network Operator (MNO) without requiring the user to provide MNO authentication credentials that are easily forgotten. The user activates the new device using credentials from an existing device (associated with the user) that is trusted by the MNO and also using a trust score provided by a third-party server that has knowledge of associations between the user and the existing device. The new device can be a supplemental device, such as a wearable device to a cellular phone, where both devices remain capable of accessing services provided by the MNO after the new device is activated with the MNO. The new device can also be a replacement device, such as a new phone, tablet, or wearable device, where the new device supplants access to services provided by the MNO for an existing device.