Instagram is accelerating the end…

Instagram is accelerating the end of their current API.

Per a notice on https://www.instagram.com/developer/ no new clients can register, and soon some basic functionality will be changed.

We will be reviewing plugins that call these functionalities and, if they are not updated, will close them in order to prevent adverse impact on users.

If you know you’re not going to want to fix this, please email plugins@wordpress.org, provide a link to the plugin, and tell us you’d like us to close it. We know that Instgram (and Facebook) have been difficult to work with this last year, and fully respect and support your decisions here with regards to your plugins.

Here is Instagram’s announcement:

UPDATE: Starting October 15, 2019, new client registration and permission review on Instagram API platform are discontinued in favor of the Instagram Basic Display API.

To continuously improve Instagram users’ privacy and security, we are accelerating the deprecation of Instagram API Platform, making the following changes effective immediately. We understand that this may affect your business or services, and we appreciate your support in keeping our platform secure.

These capabilities will be disabled immediately (previously set for July 31, 2018 or December 11, 2018 deprecation). The following will be deprecated according to the timeline we shared previously:

  • Public Content – all remaining capabilities to read public media on a user’s behalf on December 11, 2018
  • Basic – to read a user’s own profile info and media in early 2020

For your reference, information on the new Instagram Graph API.

#instagram #api

Facebook Changed Sharing Counts

Today, Facebook released version 2.7 of their API and changed the manner in which shared posts are counted.

That would have been okay, except they also turned off the part of the 1.0 API (the one that didn’t use versions in their URLs because who needed that?) and blindsided everyone. Reading the Facebook Dev Changelog didn’t make that any more sensible to me either. But what I can tell you is here are some affected plugins/services:

  • Jetpack: https://github.com/Automattic/jetpack/pull/4879
  • Genesis Simple Share Buttons: https://wordpress.org/support/topic/facebook-share-counts-not-showing
  • SharedCount: https://www.sharedcount.com/notes/facebook_api_shutdown.php

Anyone who has a plugin (or theme) with sharing buttons that count MAY be affected. If someone can come up with a way to scan the repository for impacted plugins, let me know and I’ll be happy to do that and email as many of them directly as we can.

#api, #boom

Google Maps JavaScript v2 API To Be Removed

If you’re using the Google Maps JavaScript API v2 (and 78 of you are), your plugins will break on May 19th. This means we’ll not be accepting any plugins that use the old code (and probably will close your plugins that do if you don’t fix ’em).

From Google, Google Maps JavaScript v2 (Deprecated)

The Google Maps JavaScript API Version 2 has been officially deprecated as of May 19, 2010. The V2 API will continue to work until May 19, 2013. We encourage you to migrate your code to version 3 of the Maps JavaScript API.

The Google Maps API lets you embed Google Maps in your own web pages with JavaScript. The API provides a number of utilities for manipulating maps (just like on the http://maps.google.com web page) and adding content to the map through a variety of services, allowing you to create robust maps applications on your website.

The Maps API is a free service, available for any web site that is free to consumers. Please see the terms of use for more information.

To use the Maps API on an intranet or in a non-publicly accessible application, please check out Google Maps API for Business.

So please update your plugins.

(Props to Kailey Lampert for this post)

#3rd-party, #api