Utilizing message metadata for improving user interface presentation
摘要
說明書
At operation 1108, the subscription management component 116 can determine authentication data associated with a user associated with the authorization indication. In some examples, authentication data can be required to authenticate the user and/or the user computing device requesting the subscription. In such examples, the subscription management component 116 can determine authentication data associated with the user. For example, the subscription management component 116 can access authentication data associated with the user that may be stored in the datastore 122. In some examples, the subscription management component 116 can prompt the user for authentication data, for example, via the subscription user interface or another input mechanism (e.g., a pop-up, text message, email, etc.). In some examples, the subscription management component 116 can send the authentication data to the third-party server(s) 154, as illustrated at operation 1110. In at least one example, the subscription management component 116 can request consent from the user prior to providing such authentication data to the third-party server(s) 154. In some examples, such consent can be implied. The third-party server(s) 154 can return an authentication indicator (e.g., a token), which can be stored by the server(s) 102 to indicate that the user is authenticated to receive notifications via the subscription. That is, operations 1108-1110 can enable the establishment of a verified connection between user accounts of the user on the communication platform and the third-party platform. In an example where a user does not have an account with the third-party platform, the authentication data can be used by the third-party platform to create an account for the user.
