My various Google Gadgets embedded on Google Sites broke yesterday with the deprecation of OAuth1 by Google. I am unable to find a working example of an oauth2 gadget that works on Google Sites.
Could anybody kindly confirm that this is indeed supposed to work and do you have an example? :)
My fear is that the note on this page: https://developers.google.com/gadgets/docs/basic
Note: Writing OAuth gadgets is no longer supported.
spells bad news for me!
Related
my dev and I would like to implement the google picker on our website. It will allow the web-visitor to upload their files from their Google drive to our website.
My dev is now trying to get the API for the google picker however they are asking for a "demo video that showcases the process to request an OAuth token" and we were wondering how we should do it when we don't have the API from google.
We are doing all of this on the staging site and we were wondering how are we suppose to do this demo video when the API is not provided and not installed.
please enlighten us, thank you!
See the question How can I make sure the verification process is as streamlined as possible? in the FAQ. It explains what the verification team is looking for with the video. Mostly it's just about showing how your product uses OAuth and the various APIs -- in your case how it asks for access to Drive, how the picker is used, etc. You're showing the integration from the user perspective.
Looking at this site http://www.thefancy.com/ and clicking the Sign up button followed by the Twitter option it brings up a window for Twitter Login.
I assume this is the JS approach to Twitter login in a similar fashion to Facebooks.
On my site I have already implemented Connect With Facebook (using JS) and to keep my site consistent I would like to know how to do this using Twitter's Sign On service.
Does anyone have any useful advice or links to help me with this - I can only find guides that take the user to Twitter's website during login and then back again to mine which is not what I want.
Many thanks
EDIT:
I did notice this on Twitter's site:
"Reminder: It is strongly discouraged to use OAuth 1.0A with client-side Javascript."
Why do Twitter recommend against using JS with OAuth while Facebook and Google are happy to go with it?
tHave you looked into Twitter OAuth? In order for Twitter to grand your site details, it has to redirect your users momentarily to twitter for them to verify this access. This link explains it a bit better: https://developer.twitter.com/en/docs/basics/authentication/overview/3-legged-oauth
Temboo simplifies the process of developing Twitter sign up (via OAuth). See here for details: https://live.temboo.com/library/Library/Twitter/OAuth/
Temboo doesn't have a JS library though, so you will have to use the REST API.
Full disclosure: I work at Temboo.
I am interested in creating a Google plus application.But I come to know that Google haven't released its api yet.Then How these guys are creating Google plus applications?
http://startgoogleplus.com/
https://chrome.google.com/webstore/detail/egmjfgoffglfaiieliagnianjiohfnhf?hl=en-US&hc=search&hcp=main
Thanks in advance.
The second one looks like the only thing it does is to allow you to access the mobile version through desktop browser, so my guess is that is "faking" the the User Agent of a mobile browser to cheat Google+.
The first one, if it just imports the photos from Facebook and adds them to Google+ it may be using the Picasa api, since it's where Google+ stores the pictures.
Even if you cannot access Google+ api just yet you can use the other Google ones to "influence" what you get in Google+. Just be creative :)
The API has now been announced at: http://googlecode.blogspot.com/2011/09/getting-started-on-google-api.html and the official homepage is: http://developers.google.com/+/
Is there a way to access the google search api, with its repository of website screenshots?
I'm afraid not.
Even so for the website screenshots Google is seems to use other services. Check on URL2PNG website footer, they are claimed to be trusted by teams of Google, also Twitter, GitHub, etc.
I'm working on redesigning an older site and I'm upgrading it to HTML5. The site currently has both Google and Yahoo site verification META tags.
I'm using HTML5 Reset as a starting template and it only has an area for Google site verification, not Yahoo. Also, the W3C Validator validates Google site verification in HTML5, but not Yahoo.
Does anyone have an opinion as to whether or not Yahoo site verification is important or useful? And does it hold any weight with SEO these days?
No.
Yahoo search is now powered by Bing.
You can remove both (Google and Bing) verification references and authenticate using other methods (DNS is best). Bing only offers meta tag and XML methods.