The Instagram API sucks a Lot.

Why the fuck I've to login with my account using OAuth2 to get posts of a PUBLIC account, it's so hard to make an authentication endpoint that doesn't require the user to enter his credentials in order to access PUBLIC content?

Fucking piece of shit

so they can limit access and not get scraped by a thousand bots...
and oauth2 is quite standard for apis like theirs (twitter, facebook, etc) or how would you fairly regulate traffic/requests to an api if its open for everyone?

@schwarmco like any other API? They give you public and private keys and an enpoint to obtain a short time token. You can throttle the requests using this. The OAuth2 would make sense for accessing the user personal data, or private profiles followed by the user.

Instagram in general sucks hard... and Facebook too.
Never understood the need to advertise every piece of your life to the internet

@Nastrand but they also provide this feature and why would you implement two different auth-mechanisms if one works for everything?

@schwarmco because doesn't cover all use cases, for example I want to show a feed with my latest ig pictures, in order to do this I've to implement in my website a mechanism where I make a request to Instagram, log in, and then store a token (which expires).

I just want an endpoint to get my last pictures, I don't think it's a really weird thing.

Ive solved it using the embed api, but I have to change manually the pictures so it sucks a lot