Today in the Bing the news search API response Json, I found that the url parameter is coming in a different way then it was coming previously.
As per the documentation at https://learn.microsoft.com/en-us/azure/cognitive-services/Bing-News-Search/quickstart#the-response
The url parameter should start with
"url" : "http://www.bing.com/cr?IG=CCE2F06CA.......www.abc.com/......"
But since today it is starting with
"url" : "www abc.com......"
It is omitting the "bing.com...." prefixes..
Please confirm if this was changed recently and any plans to support the original one ??
Please confirm if this was changed recently and any plans to support the original one .
It seems that it is changed recently. We could check the document history from GitHub.
Based on my experience, it seems that there is no plan to support the original one.
But I also recommend that you could report an Azure support request to get the help from Azure team directly.
Related
When I open a Jira issue link from a third party or copy from a clipboard I always find the URL looks like this:
https://mycompany.atlassian.net/browse/comapnyAlias-issueNumber?atlOrigin=longCharacters
I am curious what does atlOrigin means? and why do they use it?
There is a small explanation here https://developer.atlassian.com/developer-guide/client-identification/
Origin ID for links to Atlassian UI
Identify HTML links into our product user interface with a unique atlOrigin query string parameter added to the URL. This is similar to the UTM parameter used for click tracking in marketing web sites. In this context, uniqueness is guaranteed by Atlassian issuing the origin ID. For example, if linking into Jira’s Issue page:
https://devpartisan.atlassian.net/browse/TIS-11?atlOrigin=abc123
We generate a unique value for each integration so if you have more than 1 integration, please make sure we have properly associated each integration to a different origin value.
We do not recommend using this parameter in REST APIs or OAuth 2.0 flows, where this parameter might not be properly ignored.
Result is very Google Search - unfriendly to come up 😕
Issue:
First API calls only returns top 3 posts.
The next_url returns no data(data array is empty and pagination string is null)
The 4th post is suspect because I am unable to get it with API calls and it is not returned in the first API call.
Details:
Using v1/users/self/media/recent endpoint
Using Javascript to loop through calls, using "next_url" for the 2nd and subsequent call.
Using Access Token
Worked fine(returned all posts) until "the 4th post" was made
Why do I think one specific post is the issue? Because I am unable to retrieve it using the API. If I set the max_id to this post id, then I get all other posts before this post.
If I leave max_id out, the first call gets all posts newer than this post.
Verified that I am not in a Sandbox.
Has anyone encountered this before? and why would one post be breaking the next_url API call? Is there something in the post causing this?
I can't give out the IG account, sorry I know that would help, but it needs to remain private.
I am a developer on a project that makes extensive use of the legacy Instagram API. It has, for a long while now, been extremely flakey. We have experienced your exact issue many times and there is no practical solution.
However, all Instagram APIs have now (finally!) been migrated to Facebook. You should use the new Instagram Basic Display API which will be properly supported going forward.
We are having problems with returning results from Instagram API for location (lat, lng) and hashtag searches. It only stopped working in the last couple of weeks.
Has Instagram changed API without warning?
PLEASE help us.
Does anyone also have a sample get call for hashtags?
The script is wtitten in Python.
Thank you
Coby
Theres a new Instagram API update that happened in June 2016.
refer dialogfeed doc link
I really wonder how they can increase traffic on insta by setting up stringint limitations. :-(
The Doc stats - "This aims to limit third party inadequate uses of Instagram user contents and to increase trafic on Instagram."
With the Kimono Web, in the crawled payload there was always url and index field in every source URL JSON. But with the desktop, these fields are missing and my product was totally depends on it.
I'm browsing the source codes of Kimono Desktop but I couldn't manage to find that part.
The index field is explained in there ; https://help.kimonolabs.com/hc/en-us/articles/203349674-Add-a-unique-index-to-each-result-object-
Can anyone help me with it ?
Thanks
I've had the same issue. I found this workaround for the missing url field with the desktop application http://mudd.com/blog/how-to-extract-vdp-data-from-your-website/
Also, in case you used the crawl scheduling feature with the Kimono web app, I found that if I edit my APIs and save them again it lets me choose a crawl frequency. I just discovered this so I'm crossing my fingers and waiting to see if it's really going to work.
I am planning to use the /media/search endpoint in the Instagram API. For our purposes we would need to use MIN_TIMESTAMP to get publications written after a certain timestamp. However, I have noticed that this parameter is available in the deprecated API, and it is not available in the new API:
This is the endpoint in the deprecated API:
https://www.instagram.com/developer/deprecated/endpoints/media/#get_media_search
This is the endpoint in the new API:
https://www.instagram.com/developer/endpoints/media/#get_media_search
As you can see, MIN_TIMESTAMP and MAX_TIMESTAMP disappear from the new documentation. However, I have performed a query with these parameters and they seem to work.
I have searched in Instagram's developers blog and I did not find any comment on this.
Are these timestamp parameters disappearing in the future?
The changes were rolled out today (1st June 2016) and you will see that now the min_timestamp is no longer taken in to account.