Skip to main content
 

Dynamic AMP Emails? Sounds familiar.....

[I worked on the LinkedIn implementation since it was all oauth based..]


https://techcrunch.com/2010/12/16/hotmail-active-views-look-to-make-email-interactive/





 

So what are people using to get photos in from old-school cameras?

The Eye-Fi X2 is now basically useless for this:
- They used oauth 1 for their "PICASAWEB" upload feature.  This is now broken.
- They used iPhoto APIs to upload photos.  The new Apple Photos App doesn't have integration hooks, so again, nothing.

Their new offerings only upload to their own cloud, so I'm left with useless hardware.  Yay progress.


https://community.eyefi.com/






 

Care about standards? From my comment from Jeff Dean's post at http://plus.google.com/112317652221071509598/posts/Wd1SamQcvpQ

Here's some things you can do to support standards at Google:

-- Look at the pages your team generates the way Googlebot does:

http://www.google.com/webmasters/tools/richsnippets

Add standard schema.org and html5 markup.

-- Discuss standards with the scant 200 other Googlers at  http://g/standards-discuss

-- Participate in a standards mailing list/group.  Plenty available for individuals at IETF or W3C.  See standards-discuss if you want to participate as a Googler on corp-oriented bodies.  Standards often suck because they're written by the standards/industrial complex instead of actual implementors.

-- Participate in an open-source project that implements a standard.  These reference implementations are often poorly or insecurely coded.  (For example a few people contributing to Apache Oltu would make Java OAuth that much better)

-- Consider exposing your amazing well-crafted stubby API via Apiary.  Be extra careful to not break compatibility for a whole year.   Write lots of integration and conformance tests.

-- Be like Vint.  Suit up.

-- Above all have fun!


http://www.google.com/webmasters/tools/richsnippets






 

Okay Googlers -- if you were unhappy that Events was a closed dogfood you have your chance to participate in the most open dogfood we've ever done.

Here's some simple things you can do:

- Are you using proper schema.org markup?  Are your comments http://schema.org/Comment? Are your reviews http://schema.org/Review?
- Do you have a user history for your service?  Investigate if it's possible to send these moments to frame service.  I can connect you with the right people.
- Do you request OAuth scopes for your api-based service?  Consider using plus.moments.write to send us active and passive user activity.

Docs are below, feedback will be gladly taken (and I just might send you some Google+ schwag as a token of appreciation)


http://developers.google.com/+/history/






 

We had alerts fire for facebook downtime today. Must have been ugly if it brought down their oauth apis...









 

Embeds United!

I'm somewhat alarmed that there really isn't a "Life of a Widget/Embed" that has best practices on how to embed Google Content on third party sites.

Has anyone tackled this before? Obviously +1, adsense, youtube, maps, analytics and others all use their own mechanisms.

Is it time to consider deploying common infrastructure for these use cases? Especially for systems that require the ability to identify a Google user?

So here's my proposal.

* Use oauth2 semantics everywhere: tokens and api requests.
* Use a single bootstrap system to identify js domain, collect API keys as needed.
* Generate two new types of OAuth tokens that do not contain user info.
- 'Anonymous-by-domain'
- 'Anonymous-by-domain-by-api-key'
* Allow an account widget that can move you from anonymous -> identified -> authorized. (including multilogin, signin and account registration)

If all the various embeds used this common system we'd have a way to enable personalization on third party sites more easily and provide a clear way to go beyond.

Am I barking up the wrong tree?









 

Just registered for this event with the hope that I'll be able to get OAuth or XFN support in MediaWiki. Sadly EventBrite has every share mechanism except the +1 button..


https://www.mediawiki.org/wiki/San_Francisco_Hackathon_January_2012






 

Bye bye OAuth-Wrap!

The Hotmail account feature in Google+ now uses OAuth 2.0 to fetch your contacts. Looking forward to talking to more OAuth 2.0 enabled endpoints (ToS/BD willing!)

Congrats to Yaniv Shuba and the rest of the team!









 



Turns out we're prompting people to connect 'Yahoo' in Japan -- it's not the Yahoo that we all know and love here. Different URL, different ids, etc.

I'd love to get some igraph rules for these guys.. Anyone willing to help? Also curious of oauth based apis are available.

TIA...









 

 

Learn more about OpenSocial at Duboce Tech Talk right now!

Activity Streams, Oauth, Shindig, enterprise apps and more....

At the very least come by at 5pm for beer&wine!









 

Answer by Paul Lindner for OAuth::Problem (parameter_absent) http://ff.im/-m2MeN

 

Comment by Paul Lindner on LinkedIn API returns 'Unauthorized' response (PHP OAuth) http://ff.im/-m2zoQ

 

Lots of technical info on our new OAuth features. http://lnkd.in/8iZbsK

 

LinkedIn now supporting more ways to use to perform authentication -... http://ff.im/-jyfyL

 

lindner opened issue 2 on episod/oauth-dancer http://ff.im/-ivYsy

 

lindner opened issue 1 on episod/oauth-dancer http://ff.im/-ivYsw

 

Attending IETF OAuth meeting via webex - http://www.ietf.org/meeting/77/webex.html Good Stuff http://ff.im/-hVlfF

 

lindner started watching episod/oauth-dancer http://ff.im/-gU8mD

 

Auto-Detecting Approval ‎(Google OAuth & Federated Login Research)‎ http://ff.im/-5E2MT

 

OAuth Playground http://ff.im/-3ykvj

 

even better the hi5 implementation uses oauth and portable contacts! re: http://ff.im/2mrB1

 

Checking in fixes for shindig to deal with the OAuth vulnerability http://ff.im/-2iRjd