September 2, 2019
Related Articles (579)
For a few days, Facebook was providing a user's phone number and address available, with the user's permission, via its Facebook Graph API. Likely fueled by distrust of Facebook's previous approaches to privacy, users and press reacted negatively to the concept. Based on this feedback, Facebook reversed its decision and neither phone or address is returned to applications at this time. Privacy is a big concern, especially for APIs, but Facebook took appropriate steps for gaining user permission. The reaction to Facebook's platform change was an overreaction, which points to a need for more granular privacy controls and a better method of granting access.
Stormpulse, a weather intelligence company, has launched a risk management solution (i.e. Riskpulse) which includes an API that third parties can integrate with existing systems: the Pulse API. Riskpulse moves beyond weather related risks to business. Riskpulse constitutes a comprehensive risk management solution that delivers insight into crime rates, travel alerts, environmental risks, and more.
Google has evolved its bot-detecting reCAPTCHA API again. reCAPTCHA v3 goes beyond distorted text and identifying signals. v3 monitors a site user's interaction with a site and provides a score to the site owner/developer. The developer can use the risk score to evaluate needed actions.