I got this email from dropbox dev:
I clicked all the links looking for the v2 endpoints but cant find it anywhere. I click documentation and then it tells me to pick an lanuagues like js or something.
Is this a bug in the email? Did they forget to point to the v2 endpoints that are found here: https://www.dropbox.com/developers/documentation/http#documentation
I know this endpoint link only because someone on stack linked me to it in the past.
I voted to close, since this doesn't belong on Stack Overflow, but thanks for the feedback on the site. The first link in that email goes to https://www.dropbox.com/developers/documentation, and if you click on "HTTP" on that page, you get to what you're looking for. (This is the same as the "HTTP" link on the left-hand nav of the site.)
Is there a different phrase you were looking for other than "HTTP" that would have helped to make this stand out?
Also, the second link goes to the API Explorer, which also lists the endpoints. Each endpoint there has a "documentation" link which goes to the appropriate endpoint in the HTTP documentation.
Related
I wondered if someone could answer this question.
When putting in place 301 redirects for an old website to a new website. Would the metadata from the old website show on Google. If so, what is the best way to resole this?
How will our meta description, google preview and such like be impacted by the redirect? Meaning, will the current ones still show up once the redirect is in place, or will it be the meta description and google preview of the url it is being pointed to?
I guess that question applies to pretty much all of the current site settings/errors. Will we still be ranked on these and therefore is it in our interest to fix any errors with on the old site or should all the focus be on the destination domain, i.e. will any errors or settings on the referring domain no longer matter?
A google search -html map element site:w3.org- returns a hit with the link advertised as "https://www.w3.org/wiki/HTML/Elements/map". (That appears both at the bottom of the browser window, and in the popup i see by clicking the ellipsis. The actual link behind the hit text is a great long google hash, but when I paste the address, that should not matter. I think.)
If I click on the link, OR paste that w3.org address into FF or Chrome's address bar, I go instead to https://developer.mozilla.org/en-US/docs/Web/HTML/Element/map.
Why? Is W3.org really redirecting me to Mozilla? While I have great faith in Mozilla, I thought W3 to be the "ultimate authority". If so, how do I find what they have to say on the topic of a MAP?
Sorry if the "tags" are inappropriate, I cannot think of others, nor a better way or place to ask this rather embarrassing question.
The W3C Wiki does appear to have shut down and redirects to MDN, but the W3C Wiki was never authoritative (and, afaik, always user editable).
The HTML specification used to be available at https://w3.org/TR/html5/ but that now redirects to WHATWG's site since they write the specification these days.
I have been looking into how to venmo deeplinking schemes and am trying to open a user's account based on their username. I looked all over the internet for this and closest I came was this blog post. The person in the blog post is so close to achieving what I'm going for but I still can not figure it out. I tried changing up the "venmo://users" multiple times trying to open up a profile with a username but nothing has worked. How can I accomplish this?
Thank you in advance
I found a tricky way to finding out Venmo's deep link to a user's account. On this site https://app.urlgeni.us/ you can paste the URL you're trying to get the deep link for and it'll provide iOS and Android information.
Also, by reviewing how it works, it provides an API (https://app.urlgeni.us/api/internal/test_url) to which you must invoke (POST method) and it'll return the deep link, by sending a JSON input as the following:
{"url":"venmo.com//UserName"}
Response will include something like:
"android_scheme": "intent://user?user_id=XXXXXXX#Intent;package=com.venmo;scheme=venmo;end",
"ios_scheme": "venmo://users/XXXXXXX"
I am using the Instagram Rest API for a simple application and I've hit a bumb.
The call https://api.instagram.com/v1/tags/{tag-name} works fine (I also have the ?accesstoken=XXXXX... appended).
But the call for basic user information is not working. Not in the developer console and not in the browser when modifying my own URL.
Has the method been removed? Is it broken? If no one has an answer for that; How do you contact Instagram to report the broken link?
Thanks to #CnapoB I managed to realise the call wasnt what I was looking for! And also he showed me the Instagram Endpoints doesn't show the easy way!
https://api.instagram.com/v1/tags/{tag-name}?access_token=ACCESS_TOKEN
might as well be
https://api.instagram.com/v1/tags/{tag-name}?client_id=CLIENT_ID
which means you don't have to have the user login to the application etc.
Thank you so much for this!
What I wanted to do was instead this: (example: tyrabanks)
https://api.instagram.com/v1/users/search?q=tyrabanks&client_id=CLIENT_ID&count=1
I am having a go at trying to get the Facebook API SDK for ColdFusion working.
https://github.com/affinitiz/facebook-cf-sdk
I have followed all the steps and it seems to work well (using only server-side login).
However, if I leave the page for say, an hour, when I return and refresh the page (which was showing my profile name and friends list) it shows up with an error that I am unable to get rid of, unless I clear the cookies.
Is there something I am missing with this FB login? Am I meant to be checking against something manually in order to persist the session?
Looking at my cookies, I have the following stored:
fbm_155030275875
fbsr_155030275875
CFID
CFTOKEN
It's all new to me, so I'm a bit lost. I can't see anything in the docs for the SDK about this and Googling the error brings nothing.
I have attached a screenshot of the error.
I'd appreciate any help you can offer!
Thanks,
Michael.
I'm not familiar enough with that particular project, but in general, your code should be requesting the various Graph API calls, and requesting the token as necessary. If the token has expired, you request a new one. I'd expect the facebook-cf-sdk product to do this, but again, I'm unfamiliar with it.
Good news is, the Facebook Graph API is just a series of HTTP calls. See my talk at NC DevCon for an example of logging in and making some graph calls: (a bit long; go to about the 1:42:00 mark)
http://textiles.online.ncsu.edu/online/Play/61d0900d63fd4c1cb862622d1c8e13521d?catalog=35211b84-031b-4a18-8875-506f09b9b3a7
GitHub repo:
https://github.com/bdcravens/ncdevcon2012-handson-auth (note the branches - check out the step4 branch)
These don't answer your question 100%, but they may be a good starting point for you.
Ok, I figured out how to solve this issue using a solution someone provided on Github. I just wanted to post this here in case someone else encountered the issue and wasn't sure how to solve it. In my case however, after I applied the solution from that post was I need to do a page refresh. Link below.
https://github.com/affinitiz/facebook-cf-sdk/issues/31