“Friends and family” is a subjective term that Instagram doesn’t really define, but you should think of it as the most important people - or even brands - in your life. With the algorithmic feed, Instagram claims people see 90 percent of posts from their “friends and family,” compared to around 50 percent with the reverse chronological feed. It’s not known exactly how much more time, but that’s great for Instagram’s business: More time spent means more ads seen, which means more revenue for Instagram.īut Instagram frames it differently: People spend more time in the app because the algorithmic feed means people see more important posts that they would otherwise miss. The most important, in my opinion, is that users spend more time on the app with an algorithmic feed than a reverse chronological feed, a spokesperson confirmed. “We’re not thinking about this at this time,” said Julian Gutman, the product lead for Instagram feed, in a recent press briefing with journalists intended to explain how Instagram’s feed actually works. So will it give users the option to revert back to seeing posts in the reverse order in which they’re shared? The company knows it’s a popular request.
#INSTAFEED NOT TAGGING SOFTWARE#
The only way I can see around this is to make multiple requests with multiple access tokens (one per user), and then combine the responses yourself afterwards.It’s been more than two years since Instagram started using a software algorithm to power its feed - which means that posts show up based on what Instagram thinks you want to see, not just the newest posts first.Įver since then, though, the company has been getting complaints from users who miss the old, reverse-chronological timeline. So, if you and I are both users in the same sandbox, we can supply the sandbox client_id and our own individual access_token, and then use an endpoint like /users/self/media/recent/ to get our own media, but we can't get /users//media/recent because that endpoint requires public_content permission, which is no longer being granted, and is never granted in sandbox mode anyway. It really just acts as a scope which defines which user's access tokens are valid inside your client. Sandbox mode doesn't give you any additional access or endpoints. Here's my current understanding (matches your own, I think): I misunderstood some of the recent changes, and Instagram's own documentation hasn't been updated and still has examples which no longer work. Reply to this email directly, view it on GitHub, or mute the thread. You are receiving this because you commented. I wouldn't expect to see functionality like requesting per hashtag come back, though. The library would need to be re-written to work with that API. The future of the instafeed.js is unclear however, as Instagram's API is being replaced by Facebook's OpenGraph API, and the restrictions there are quite different. More complex things like showing all public images tagged with #somehashtag do not work for new access tokens. So, the common use-case of "Show my latest n posts" works fine for now. That limits you to the 20 most recent posts for that user. The major change is in the direction of locking down content - you will only be able to get posts from a user you have an access token for, and in sandbox mode. Yes, Instafeed.js does work - within the limitations of the Instagram API (which have changed, and are still changing). I know is pretty busy at the moment, so I hope I'm not stepping on toes! Here's my unofficial take - I've been following the Instagram API changes and this library pretty closely.
0 kommentar(er)
