YouTube shows that they haven't even watched the screencast they asked me to make, just flat out denied without spending any time on my API request.
It's their product and they can do whatever they want with it, but the annoying thing is that they had released an API for people to play with, people built features around it, and now the features do not work. This kind of disrespectful dismissal make me really reluctant to spend time integrating other APIs in future things I make.
In this case, though, Instagram gave people over six months to transition to the new process and workflow, and for us, our approval took less than a week. IMHO, this is a good example of the right way to transition applications over.
>> Any app created before Nov 17, 2015 will continue to function until June 1, 2016. On that date, the app will automatically be moved to Sandbox Mode if it wasn't approved through the review process
I'm really not sure what more people expect instagram to do.
My issue is that they only will give "basic" permission to 3rd party apps? (which it seems like it under their valid use examples). My app DOES help individuals share there own Instagram photo content (like Tinder profile connects with users Instagram photos) but I also need public_content and follower_list.. and not sure if they will just deny with "one off project!"...
There were also a lot of spam apps (buy likes/followers) on the App Store/Play Store and this move removes most of them. They're also avoiding a Tweetdeck situation when a 3rd party client gets too big to ignore. Good for them, bad for users.
Disclosure: I made an Instagram client for iPad (http://retroapp.net). Funny that since some apps have moved to private API and now can do more than public API (no upload, no Direct access).
Facebook also shows you time sensitive things from yesterday ("come hang out with me tonight!"), to increase your fear of missing out.
> As we begin, we’re focusing on optimizing the order — all the posts will still be there, just in a different order.
Also the "promoted post" feature which they have in their new business tools looks like down the track it will incorporate a feature where businesses can pay for their regular Instagram photos to appear in more feeds. Which means even more that the `/posts` endpoint which you hit as a user is controlled by Instagram
Has anyone ever said, "ya know... Something's not right about the order of my Instagram feed. It seems to be all chronological!"
We asked for this.
I now post very rarely and almost never browse. Occasionally I'll look up a particular hashtag relating to some car/motorcycle I like, but that's basically it.
The curated feed shift (has that happened yet?) was also very bad news for me.
So I went ahead, and deleted my account (that was new, but already had about 100 photos or something).
They later "unchanged" the ToS, but I won't make the same mistake twice ;)
This has happened with so many services over the years, that one would think developers would be more enthusiastic about educating the end user with libre software. I do that aggressively with people I know. Too much to ask?
It's just that for services like that the wealth is the data, they don't want 3rd parties to profit from their precious data. Instagram (free) API was shitty anyway, so I bet not a lot of developers was using it. Twitter API and data is far more useful.
Won't be long before I can't access Instagram altogether without an account, much like Facebook.
Instagram can't revoke the keys because that 'd kill the app for those who don't upgrade their apps all the time, the only thing they could do is to pressure the app stores to take apps down - but I wonder on what legal grounds?
I just can't understand this, business X wants to embed their own damned feed on their own page, how should they do it now?
I've hacked together a way to use unofficial API https://instagram.com/query but it's a bit iffy to use this.
Maybe it's because their mobile website is finally quite good, but looking at the Facebook Web Messenger story I'm surprised they go that route.
Because Facebook and the like are free, they evade existing competition laws. But it's not unreasonable to ask, as a society, that these huge companies take on some special responsibilities. That might well include something about openness.
The closing of the Instagram API made me reflect on the whole situation:
The fact that we created that data.
Here is an analogy. If I buy a piece of paper and it contains an EULA that says that any works written on that paper become property of the manufacturer of the paper, then would that be legally binding? If so, then do we want to live in a world where paper manufacturers have control over our intellectual property?
Note that paper is a commodity product, but the same holds for online video services, and messaging services. The ones we are using today have no or little competitive edge over other services (other than network effect), they were just lucky enough that we chose to use them.
Alternatively we can ask: are we as a society better off if we allow companies to demand the rights to user generated content, or would we be better off if we forced them to open up access?
So, a app needs to ask for a login and password each time it access Instagram?
Instead, you use OAuth to fetch an access token. This is far better for the user - they can revoke your app's access without changing passwords, and without all their other apps losing their connections.