Remove Instagram source from Tagregator

[iandunn]

It seems like our use case is no longer supported by their API anymore. All "apps" are created in a locked down sandbox mode by default, and in order to get access to real data, it has to go through an approval process.

During that process, I get this:

This use case is not supported. We do not approve the public_content permission for one-off projects such as displaying hashtag based content on your website. As alternative solution, you can show your own Instagram content, or find a company that offers this type of service (content discover, moderation, and display).

You can find more information in the ​Permission Review documentation.`

Related #2907

@coreymckrill, were you able to get an app approved when testing #2907? If not, we should probably just remove it entirely.

[coreymckrill]

I'm pretty sure it worked back in December. Maybe this is a new policy?

It looks like WCUS 2017 just used the sandbox mode to display their own posts, which seems like it's still a legitimate use case: ​https://2017.us.wordcamp.org/social-media-stream/

[iandunn]

Hmm, that's a good point, I guess it's still useful for that purpose.

[xkon]

Hey, even though this was closed I just wanted to reply for clearance, the actual 'non-public access' was a thing on Instagram even before I took the tickets to patch it up for the translation day. That's why I thought of adding the SandBox mode when I did the changes.

I will be setting up <meta> again and everything soonish though so I might take another look as they made more API changes since the FB graph merge (or whatever they actually did in the end).

I could definitely work on re-wording everything so the users can understand what SandBox (account-posts) is and even gather all Tagregator tickets and bundle them up for a re-new on whatever I can tackle ^_.