I've been using instagram's real time push api (http://instagram.com/developer/realtime/) for a long time to get updates on a specific location. I use the highest possible value for "radius", which is 5000m . For the last 4 weeks, I have noticed that I received significantly less updates through the API (but not zero). Other applications seem to have the same issue, like http://now.jit.su/ . I also filed a bug report at instagram, which went unanswered.
My questions are:
- has anything changed in the API?
- has anything changed in the app (so that not every photo will be published)?
- is anyone else experiencing this issue?
- is there anything I can try to get it working again?
I know this is not exactly a perfect SO question, but I was not able to dig anything up on google, and the instagram developer pages direct here for support. Any help is greatly appreciated.
Had some communication recently with a contact at Instagram and he mentioned that Instagram's real-time functionality will be limited to only user subscriptions in the future.
Apps created before November 17, 2015 will continue to receive updates but are being sampled because of the load they are experiencing and the fact that the architecture used for this does not scale well. He also mentioned that, as a result, real-time subscriptions will be deprecated for Tags, Locations and Geographies.
The developer guides also have some information regarding this:
OLD: https://www.instagram.com/developer/deprecated/realtime/
NEW: https://www.instagram.com/developer/subscriptions/
I am using https://api.instagram.com/v1/users/self/feed?access_token=AccessToken&count=100 to get my feeds.
You might be missing count in your api or let me know which api you are using
Related
We're trying to setup a referral tracking program for a chrome extension we developed. To track reoccurring subscriptions we'd like to be able to poll the Subscription Status and I was able to find google.payments.inapp.getPurchases in their documentation here: https://developer.chrome.com/webstore/payments-iap#get-purchases
I was wondering if it was possible to poll for the order number associated with the purchase. This seems to be a way to uniquely tie and track a user to a subscription and also lets us correlate the info available on pay.google.com
Any suggestions or information is appreciated! Thanks.
Response I got back from the Chrome Developer Support:
Thank you for contacting Chrome Web Store Developer Support! In
regards to your question, unfortunately, we are not supporting polling
the associated order number at the time. However, I absolutely agree
with you that it would be very helpful for our developers in the CWS.
I'll be glad to convey your message to the pertinent team to discuss
this topic.
ServiceStack authors/community: you have done impressive job!
Outside of SO, I was wondering if there is an up to date list of products/apps using ServiceStack?
Or maybe ServiceStack app/architectural patterns for larger apps (with MQ) ? I looked at some of the suggested demo apps in SS github and I might have missed it if there is any, but just looking for something bigger/larger to explore apps with big numbers of domains. Maybe a fake subscription saas online app for some fictional rest API ? ...
I obviously am after reference materials to have SS in the list of contender framework for an upcoming project.
Anyways I hope I didn't miss a reference from SS large amount of documentation!
StackOverflow isn't the right place to ask non-technical questions like this, you can try the Google+ ServiceStack Community if you're not a Customer, or the ServiceStack Customer Forums if you are.
I previously answered a question similar on broadly Who's using ServiceStack in January 2015, since then ServiceStack Customer base has grown considerably where we have several Fortune 500 Customers, unfortunately we're not able to disclose any specific Customer info as we have several NDA's with large companies prohibiting any disclosure which we've extended as a matter of policy to never disclose any of our Customer details for Marketing purposes or otherwise.
So for specifics you'll need to ask the Google Community directly where some of our Customers may volunteer their info themselves.
A good starting point is to study ServiceStack apps in GitHub.
I have experienced significant variability when using the Instagram Subscription API. For the most part, the API will not post updates to my end-point as specified during the subscribe initiation. My understanding is that the subscription is configured correctly as any of the updates from my personal account are received.
There seem to be reports across the web talking about significant delays. However, it is my experience that accounts that work do so within seconds but in most instances no subscription messages are never received.
There was discussion on the web also regarding queuing of updates sent through to the subscribe API. Which may make a little sense, however a queue would suggest that updates would be received eventually.
I have requested basic permissions, which is sufficient to request public media from each registered account. Yet, there I have a gut feeling that these permissions could be the problem, so I have started the process of requesting public_content.
At this stage there seems to be a number of developers experiencing similar issues, yet no resolutions.
Has anybody been able to resolve this issue?
I'm subscribed to aspect=media object=user and experiencing a similar issue.
For some users, I'm notified 95% of the time. For other users, I've never been notified of a single post.
In this post nithinisreddy mentions that the data is being "sampled". I think this is the reason. Hopefully it improves after the tags/locations subscriptions are deprecated.
David of the foursquare-support-Team directed me here to leave my question for answering here...
We are currently thinking about publishing our own venues on foursquare - about 1000 of them and more to come. We would love to offer a mayor special like "50% off the bill".
Getting the information, that the mayor just checked in: No problem here - already tried to implement that and it works.
But as we are going to give money away with our 50%-special, we absolutly need to be shure, that the person who checked in is certainly inside the venue.
The current fraud-detection does not work good enough for us - today I checked into one of our test-venues, when I was about 25km away. No good :(
Here is one solution I would love to see implemented at foursquare to solve our problem:
If "trusted checkins" are enabled, the venue can still be visited by searching for it or using its URL. When checking in this way, you are awarded the regualr points, but you cannot gain any mayorship or badge (like when checking in via the mobile foursquare website).
By using an API-call, a trusted-checkin-id is generated (for example venueid_token), that can be displayed to the user by a QR-Code, NFC-Tag, etc. When this special venue-id is opened, checkins are "trusted" and are rewarded with mayorships, etc.
Upon calling the same function again, a new trusted-checkin-id is generated (venueid_newtoken). Using this new id to checkin, you get all the benefits. Using one of the old special-checkin-id, will not give you those perks.
Of course, trusted-checkin-ids can only be generated by an account associated with the venues in question.
Using this - I think quite simple system - we could present our users QR-codes to checkin and be shure, they cannot cheat.
Additionally, the beauty of this soultion is, that it won't require any change in the mobile applications already deployed by foursquare. Everything can be done directly on the foursquare-servers.
I would love to hear from you girls and guys at foursquare-engeneering-hq.
Cheers,
Martin
Users are able to check in to venues anywhere, but if they're physically far away the check-in won't count towards specials unlocks or the mayorship. So while your check-in "succeeded," it didn't actually contribute towards you unlocking the special in any way.
These check-ins also don't count towards the merchant statistics, so you can look at the merchant dashboard for the venue and confirm that the "far away" check-in was not counted.
Actually, this is how Foursquare works. They allow to checkin from far away. There's currently no know way (at least for me) to avoid it. Could you please explain in more detail, what are these 1000 venues you're going to add and why do you need this 50% major-bonus for all of them?
The only way I could think off to do what you want is to create a custom application that would use FS api to post checkins, etc, but will have additional check based on location and some custom equivalent of mayorship. Basically that's what we've done to avoid fake checkins - additional location check inside of our app.
I would like to get some stats programmatically about my app; for example: total downloads, active installs...
I wish google would give an api for doing this. What do people do?
There currently is no API, and it is possible to get these statistics, but it's quite complicated (you have to get an AuthSub token for the market developer service, and then do the right requests and parse a number of GWTRPC encoded responses. These GWTRPC responses change everytime they launch a new version of the android market dashboard, so be prepared to monitor frequently whether this has happened).
In a recent chat with one of the Android folks from Google I heard that they are aware of this issue and know that it's a very popular demand by developers, so hopefully there will be a better way soon.