Attempting to download my own saved posts using
instaloader --login=XXX :saved
leads to some nasty
HTTP Error 400 (Bad Request) on GraphQL Query. Retrying with shorter page length.
From what I know, this is Instagram's response to when it detects automated activity from an account. This led to a "Suspicious activity" screen.
Looking over the code, an Iterator[Post] is created, containing all saved posts from the logged in account. This seems like the only moment that a login is actually required. Because I keep getting the 400 code, I assume the download of posts is being done through my account and triggering the alerts.
How could I logout from my account and perform the download without it being tied to my account?
I am only interested in downloading public posts and I am aware that posts from private accounts would not be downloaded.
Related
I am building a website for my band and I would like to display upcoming events on it.
When I send a request from NodeJS to the Facebook Graph API (/{page-id}/events) with the app's token, I get a response back saying
(#10) This endpoint requires the 'pages_read_user_content' permission or the 'Page Public Content Access' feature. Refer to https://developers.facebook.com/docs/apps/review/login-permissions#manage-pages and https://developers.facebook.com/docs/apps/review/feature#reference-PAGES_ACCESS for details.
Is there a way to get this information without getting a business verification and app review?
It doesn't make sense to me that I would need that high level of permission as the information page is public and events can be retrieved by browser without even being logged in to Facebook.
I am developing an app with the use of the youtube data api. Everything worked well for more than two months until today. I have got a quota limit exceeded error today and after I opened the google cloud console, I noticed that I somehow got over 70 million requests from the chrome app oauth client which is definitely unnormal. Looks like someone is abusing my extension and sending requests.
I do use the chrome.identity.getAuthToken and request https://www.googleapis.com/youtube/v3/channels?part=id,snippet&mine=true&access_token=${token} when a token is updated so that I could display the user's authorized account name (and other details) in the extension control panel.
I assume that someone programmatically revokes the access and reloads the extension thousands times a minute so that the extension keeps sending the requests to get the user's channel info.
How do I have to handle such situations correctly? Is there a way to find that user an ban him from using the extension?
We have an approved app for public_content on Instagram's API. But would like to confirm expected behavior after the latest API changes.
Previously (prior 2016 API update), using a user authenticated token and this endpoint /tags/[tag-name]/media/recent, we could fetch all the posts with a given hashtags from public users as well as private users, given they were followers of the authenticated account. Meaning, if you could log into your IG account and see that user's media, than our app would be able to grab that media as well through the API using your authenticated user token.
Recently ( start of 2017? ), we started noticing that the returned media doesn't always include the private users that are your followers. We can still get all the public user hashtagged content, but the private user's content was hit or miss. And we can't seem to figure out any pattern or rule to it.
Has anyone else faced this issue? Does anyone know what the official stance is from Instagram as it relates to a private user's photos who follow a certain account, and your app has that account's authenticated token.
You can't get anything from private followers even if the user you're logged in as can see them from the client.
This was done because, in the past, some applications were getting the media from private followers via the API and saving them locally. Then, these applications were not properly protecting these private images from search engines and web crawlers. User's complained about their private images showing up on Google images and so, here we are.
You also can't see bio or the follower count of private users even if the user you've authenticated with can see them in the application. Basically, only the public-facing information about private users can be accessed with the API regardless of who you've authenticated with via the API. That means only the profile picture and username can be accessed.
This issue has been posted many times before but I haven't found a solution yet. I've contacted Instagram Developer support but a week later I've still had no luck or a response form them so hoping someone here can help me out. My app has been approved by Instagram for basic permissions.
Doing a Form POST to https://api.instagram.com/v1/subscriptions/ with all the relevant data (callback_url, object=user, aspect=media, verify_token, client_secret, client_id) to create a subscription for Instagram User Subscriptions yields the error: APISubscriptionError - Unable to reach callback URL
The callback URL I'm using has logging on it to log all requests which works
when accessed directly via a browser. Using the logs I can see Instagram isn't even reached my callback URL.
The callback URL is accessible publicly over the internet and the domain is being used in production.
The callback URL implements both GET and POST methods (even PUT just in case).
Worked a few weeks ago using a UAT URL.
The callback URL still returns the 'Unable to reach callback URL' with http or https.
I've changed IP addresses, used a VPN and run the post script form different locations.
Tried different parts eg domain.com/instagram/subscriptions or
domain.com/instagramsubscriptions
-Tried a different sub domain and different URL.
Have deleted all subscriptions using the DELETE request
Any help or suggestions would be greatly appreciated.
I'm using a javascript code (instafeed.js) to connect to the Instagram API and get the last photos of my Instagram account. The problem is that the thing works for a few days and then the token I got from instagram "expires" or something and it stops working. It throws me Uncaught Error: Error from Instagram: The access_token provided is invalid.
I believe (I might be wrong) it's because I never sent my "app" for review and they are giving me a "sandbox mode" token. Or should I be able to use their API for this simple thing without approval?
Should I send my website for review or is this not an intended use of their API? And if it's not, what should I do?
You should be able to use API in sandbox mode to access your latest 20 posts. You dont need to get reviewed.
Not sure about access_token expiring, in live mode it never expires, so I expect sandbox to be same