You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, Pings do not include any information about the application used to create them. This opens for several possible forms of abuse:
A spammer may trick the user into authorizing an application, and post shady links that appear to be posted by a legitimate user (something similar is happening on Twitter, there using DMs, that - unlike Tweets - lack application identification).
An application that auto-posts pings may be difficult to identify, if it does not add any identification (such as a "via …") to the text itself.
Without knowing what application is creating unwanted pings, it's difficult to deauthorize the correct one, and may lead to deauthorization of wanted services, which benefits neither the user nor the application's developer.
Right now, Pings do not include any information about the application used to create them. This opens for several possible forms of abuse:
Without knowing what application is creating unwanted pings, it's difficult to deauthorize the correct one, and may lead to deauthorization of wanted services, which benefits neither the user nor the application's developer.
(Also, PLEASE do not follow Twitter's example and force your developers to extract this information from HTML Links)
The text was updated successfully, but these errors were encountered: