I developed an android application ( https://market.android.com/details?id=hr.cloudwalk.vg ) that uses Foursquare API and I submitted my application to Foursquare app gallery. It was several days ago and it still isn't showing in gallery although dedicated app page is accessible on: https://developer.foursquare.com/app/foursquare_venue_guess
Is there some sort of approval process and I just have to wait longer? Will I get any answer whatsoever from foursquare? Is there some support mail or support form to contact them about it?
I guess I could be more patient but it was easier to ask than just wait... :-)
There's a manual approval process that happens on an arbitrarily random irregular basis. Be sure that your app follows foursquare's Trademark policy https://foursquare.com/legal/trademark and attribution guidelines: https://developer.foursquare.com/overview/attribution, otherwise it will be rejected
Related
My team has built an app that uses the Azure Face Detection API to upload a user's selfie and return some basic info. We POST this information to the West Europe server, as described on this page (https://westus.dev.cognitive.microsoft.com/docs/services/563879b61984550e40cbbe8d/operations/563879b61984550f30395236)
I need to understand what happens to the image data in terms of storage, retention, generated metadata, etc. - essentially all info around GDPR requirements. I understand from this page (https://azure.microsoft.com/en-us/blog/microsoft-updates-cognitive-services-terms/) that "Cognitive Services customers own, and can manage and delete their customer data" but I cannot see where I can manage this data in the Azure console. I have also looked in the following places without luck:
https://www.microsoft.com/en-us/licensing/product-licensing/products
https://privacy.microsoft.com/en-gb/privacystatement
Can anyone show me where I can manage this data, or a privacy document outlining default behaviour around privacy please?
Thanks
Ferg
I am developing an addon for Shopify platform and using the Shopify NET library I have managed to authorize the user shop and gather some data.
Now I need to charge the usage of the Addon with a monthly fee (providing 7 days trial) but I cannot figure out the flow I must follow.
I guess that I have to call Recurring Application Charge API after the user authenticates (at the callback from the authorization URL) and if the user declines the charge then I have to log him out. Is that correct?
Do I have to care for providing 7 days trial by myself or the Shopify RACharge API with manage it by itself?
What do I have to do when the user cancel the subscription or freeze it?
Can anyone point me out a document that analyze the charging flow except the Shopify Billing API which is not that helpful after all?
First question, you're right. You either have to log out the user or you just let him authed without permission to see some views or all of them.
There's a propperty on Recurring Application which allows you to define the days of the trial: "Number of days that the customer is eligible for a free trial.", so Shopify handles this for you.
When user cancels a subscription or his store is put on "frozen" status, you should make sure he doesn't have access to your App functionalities, though if it's frozen, he won't even be able to log into his store.
I am trying to build a spiritual website for one company and they are planning to embed some videos in their website.
And they are requesting me to make their videos private as they don't want the users to download them as they are collecting some amount for the classes and they would like to give those videos at a particular time on the website for the registered users.
If we go for live streaming it's costing much so we are planning to host it on the same website and remove them after a period of time.
So I would like to know what is the best way to do this?
Consider using a combination of PayPal Subscriptions and Forms Authentication. Use the PayPal IPN to get the users status (if they're paid up or not) and associate this with the transaction ID and user ID.
They will only get access to the video class page if they are authenticated. At that point, you can retrieve their subscription status from the DB and grant them access if they are paid up. If not, provide a friendly message and link to PayPal.
ASP.NET PayPal Subscriptions IPN [caveat: own blog]
How to set up a Paypal Subscription
You may have to use profiles to store extra information per user. If this is the case and you are using ASP.NET WAP (2.0+), then use the following info to set that up:
ASP.NET Profiles in Web Application Projects
Serving videos in a website can be done using either streaming or progressive download. The latter is technically similar to any other download, i.e. if users find the video's URL, they can download it.
You can write client-side code for hashing a one-time token to try and obfuscate the URL of the video file, but essentially committed users can hack their way into the download URL.
Your other option is to use DRM, which will allow you to restrict playing the file even if downloaded. But that might actually cost you more than streaming. (It will also provide better protection of your video, as streamed videos can also be saved on users' computers if they know how to).
Have anyone heard Facebook say anything about adding the possibility to specify the privacy when publishing an action? I wonder if it's something they plan for the near future or if it will take longer time for them to implement.
Background
The "App activity privacy" let's the user set who should be able to see actions published by the app. I would like my app to set the privacy for each and every action the app publishes, just as an app can do for wall posts by specifying the "privacy" field.
Edit 2012-05-24
I attended Facebook Developer Garage in Stockholm yesterday and had the opportunity to ask what Facebook's plan is. The answer was that Facebook did think a lot about adding flexible privacy settings, but decided that they want it as simple as possible for the user. They want to let the user decide the privacy settings for everything the app publishes once and the users can currently do this when they add the app. You never know when Facebook change their minds but currently they don't have a plan for decent privacy settings.
Facebook have now added the "privacy" parameter when publishing actions.
See https://developers.facebook.com/docs/opengraph/actions/
Case closed.
Edit: As Angel García Olloqui pointed out, the privacy field can only have the values ALL_FRIENDS or SELF. Pretty useless for now.
Edit: I added a more complete answer to the question.
Access token generates corresponding to your all permissions which appear on the first startup of the application. Then by using that access token app enables to get some information from user
I want to provide chat facility to my website visitors. This should be same as google chat (person to person communication). Are there any free tools available to integrate in the website? Or is there any way that we can use Google Chat's API and can integrate in our website?
Pls help me.
You can embed google chat into your web page, instructions here
I think a reasonable approach would involve opening an iframe that talks to a dynamic page. The dynamic page would be auto-refreshed by two or more clients and continously post to/read from a table that stores the ID of the session, timestamp, user name(or IP), and message for the chats. The ID of the session would correspond to the dynamic page ID and bob's your uncle.
I'm sure there are various implementations floating around, but I'd want to control this on my own. No user accounts required if you set it up correctly, thought finding other users may be an issue without accounts.
There are a lot of good embeddable chat widgets you can insert into a page fairly easily that do all the work for you.
I've tried out a few of the ones listed in the link above (mostly MeeboMe and Geesee) and don't have any major complaints. With that many choices you should be able to find one that meets your needs. Most don't even require a login.