Instagram is locking down their API and requiring all apps to go through a review process similar to facebook's. details in snarfed/granary#65.

they're mainly locking down /users/self/feed and /media/popular and sending photos outside of instagram, neither of which bridgy does, so i think we'll be ok, but no guarantees.

TODO for switching to scraping:

• poll
• mf2 handlers. (added scraping support to get_comment, get_like, etc.)
• signup. started in the [scrape_instagram](https://github.com/snarfed/bridgy/tree/scrape_instagram branch) branch.
  • if their account is protected, complain and don't finish signup.
• cron job that updates profile pictures.
• figure out backward compatibility for existing accounts. poll/propagate work ok, but...
  • data migration: remove the publish feature from all existing accts so that when they delete listen, their acct disappears correctly.
  • delete. indieauth into the first website we have for them. if they don't have any, make them add one and re-login first.
• cache comment and like counts? like we already do for twitter and G+, so that we only fetch individual photo pages when we need to. should help keep our load lower and off IG's rader for a while.
• handle /instagram/bret.io. he evidently changed his username from bret.io to uhhyeahbret, but we don't periodically refetch profiles (re-fetch silo profiles periodically to pick up new homepage links #304), so we didn't notice. plus username is the datastore entity key id, so it's tough to change. easiest answer will be to ask him to sign up again after we've ported signup. (done.)
• delete. (was briefly blocked on state isn't quoted properly in embedded JS aaronpk/IndieAuth.com#113.)