No data return for last night - onedrive

I use live sdk REST API to retrieve data from onedrive storage.
It contains no data in the response string event the status_code is 200.
I wonder if the apis.live.net/v5.0 is still alive from last night and where could I feedback this problem to?
thanks.

For support, try going to http://onedrive.live.com and click the Settings wheel at the top righ corner. Select Feedback, and once you've inputted your issue, it will be routed to the right folks.

Related

Google Play Developer Console total downloads statistic

Google was changed Developer Console views. We can't reach total downloads in new view. Is there any way to find total download's? or would i add month by month? example
i choosed time interval to all of time
All of the updates to Play Console Data are described on this help page. It looks like no recent change took total downloads away. So what you describe sounds like maybe a bug. You should contact Play Console support, which you can do via the help menu. This is on the "?" question mark icon.
The best way I found was set the period as lifetime and download csv file.
Then you can sum it easily with excel(window) or Numbers(mac).

Working with Synology Surveillance Station Web API

If is someone that worked with Synology API documentation is here
I wonder if there is any possibility to get a snapshot picture on a certain timestamp (let's say a snapshot from yesterday). I have all the recordings saved on the server grouped in videos of about ~10 min on a full day.
What I managed to do so far is to get a snapshot of the live screen with this API GET call:
http://34.59.110.237:6001/webapi/entry.cgi?api=SYNO.SurveillanceStation.Camera&method=GetSnapshot&version=1&cameraId=3&xtamp=1486308916&preview=true&_sid=$currentsid
This will get me each time I call it a print of the current screen, somehow the xtamp=1486308916 (unix timestam) won't take any consideration. I tryed with (time,timestamp,update_time), no luck, any idea ?
The GetSnapshot method from the API SYNO.SurveillanceStation.Camera ist only for the current view.
I have no idea for your problem, but look at the "List" method from the SYNO.SurveillanceStation.Recording API.

Instagram realtime get post from callback

Right, this is really working on my nerves, but Instagram has to do something about their bloody documentation.
I am already trying for a week to live update my website with new instagram posts without refreshing the page. Twitter was fairly easy, but instagram is just one big mess. Basically I use the realtime Instagram API, the callback and all that stuff is working fine, but thanks to Instagram it does not return me an ID from the post that is new, the callback only returns some basic stuff:
[{"changed_aspect": "media", "object": "tag", "object_id": "nofilter", "time": 1391091743, "subscription_id": xxxxx, "data": {}}]
with this data you are nothing, except for the Tag, but I knew the tag before this callback too so doesn't matter. It actually only tells me that there is a new post. I have tried doing the same request as when the page loads, when this callback occurs, and get the posts that are newer than those already on the page. Unfortunately I have not succeeded in this yet. I have picked the ID from the last posted instagram post, and checked if it is in the callback request, and it's not.
What am I doing wrong?
I'd appreciate some help, thanks!
Edit:
I'd like to note that this is not only a problem with the realtime api, but also with the normal API. I just don't know how to compare data so I don't get duplicates in my database(normal api), or on my website (realtime). I can't find any tutorial or documentation (Yes, I might be blind), that explains to me how to compare data. I can only find the min_id and max_id, but no explanation what these id's contains. I checked these id's with id's from results, and they do not match. It's not an ID from a media item.
I also checked the next_url, and in my logic thinking, this should be a URL to the next page (like Twitter).
Am I looking at this all wrong?
Ok strike my old answer, I changed the way I do this. Here's how I'll do it now.
I still wait for 10 hits on my Real-time subscription, when I reach 10 I send off a new thread (if one is not already running).
The sync thread queries my DB for a value, I need the last min_tag_id I used. Then I query:
https://api.instagram.com/v1/tags/*/media/recent?access_token=*&min_tag_id=*
Try it out here: https://api.instagram.com/v1/tags/montreal/media/recent?access_token=*
You'll get 20 results, and a min_tag_id value. Append that to your url, you'll see you get no results. Wait a couple of seconds and refresh. Eventually you'll get some media, and a new min_tag_id.
(You can ignore the "next_url" value they give you, you won't be using that).
Basically you only need to store that min_tag_id and query until you have no more results, that means you're done then.
When you get a subscription push, you need to query that endpoint (tag / recent).
I normally start an synchronous thread to perform this so I can answer in under 2 seconds to Instagram.
Then you parse that endpoint and look for a "next url" value.
Keep querying that end point, parsing the media and going to the next url until you find your stop condition.
For me I try to match 10 consecutive records in my DB. Basically from the tag, I store media when then meet my business rules.
The Instagram documentation is accurate and actually well written.
The realtime API is working correctly. As stated in the documentation:
The changed data is not included in the payload, so it is up to you
how you'd like to fetch the new data. For example, you may decide only
to fetch new data for specific users, or after a certain number of
photos have been posted.
http://instagram.com/developer/realtime/
You only receive a notification that an update has happened to your subscribed object. It is up to you to call the API to find out what that data is.
You can call the /tags/[tag-name]/media/recent with an access token that you have previously stored on your own server or DB. Then, you should be able to compare the data returned from that endpoint with any data you have retrieved prior, and just pull the objects that you do not yet have.

Deezer API - Get user's currently playing track

Is there any way to know the state of a track using the deezer api.
"playing" or "not playing" ?
I can't find anything in the docs... I'd like to know the currently playing track for each user of my app... Or at least the last played track.
I assume there might be some privacy issues... any thought?
We don't have a 'now playing' status but you can use the User/History fields:
GET https://api.deezer.com/user/1494543/history
That will give you the full paginated listening history of a given user, updated almost realtime (allow 1 or 2 minutes sometimes). The first result is the last song listened.
Regarding privacy, you'll need to ask the 'listening_history' permission at login.

get +1 date timestamp or for google plus activities/posts

I am trying to get some information about the post people do in google plus. In particular I am interested in the "+1"'s.
Either from the google api or directly from the google plus web site you can get the total count and name of the people who did "+1". But, I would be interested in getting the time or timestamp of the "+1"'s. Does anyone knows if it is possible or how can I do that?
Help is always appreciated
Thanks to all,
As you can see at https://developers.google.com/+/api/latest/activities, the only data we return for a +1 is a list of the +1-ers, as well as the total number of people who +1'ed the item you are looking at.
If you would like to request additional data, please file a feature request in our Issue Tracker: https://code.google.com/p/google-plus-platform/issues/list. It would really help if you could be as detailed as possible in the type of data you would like to see and how you would ideally use that data.
If you're dealing with your own website and only care about +1s for pages on your own domain, you could use Google Analytic's social information to see how +1s change over time. You wouldn't get information about who did the +1ing.