誰だよOAuthはオースと発音するとか広めたの。社内ブログでそれ書いたら、ほんとは違うじゃんかよ。それ昔の話らしいぜ？今は"OH AUTH"らしいよ。
なんか、AOLがOpenAuthってのを後でOathって変更したから、それと混ざっちゃうので、OH Authになったんだってよ。
追記
いやごめん、実際誰が広めたのかは別にどうでもよかったんです。なんか勢いでそう書いちゃっただけで。
さらに追記
いや、AOLはOpenAuthって名前を変えたわけじゃないっぽいなあ。Oauthと略して、さらにOathと発音させた、って話はほんとっぽいけど。もうどうでもいいか。
I'm looking to implementing a few of various aspects of "Open - Distributed - Social" thingy recently. The primary interest right now is to leverage OpenID endpoint URL more, because that's the URL accepted, for example, when a commenter tries to comment on my Movable Type powered blog.
For example, Vox and LiveJournal specify the blog's main index page as the OpenID endpoint for the blog's owner. Both Vox and LiveJournal have other information in the main index page, such as link to FOAF and Atom feed. Net::OpenID leverages the fact and retrieve FOAF and/or Atom feed to annotate OpenID with those semantic information.
Things are a bit different in the current addition of OpenIDs. AOL, Yahoo, livedoor, and Hatena, have the dedicated page to their users' OpenID endpoint. Those pages does not have much information except explaining that they are OpenID endpoint. Yes, nothing is wrong with that, of course.
WordPress has a cool plugin called hAvatar. Basically the plugin accepts commenter's URL either from what is manually entered, or from OpenID the commenter has signed in. It retrieves the resource from the URL and search for hCard, to grab the photo of the person (== commenter), and load the photo as the commenter's userpic. Neat.
I am trying to implement the same function in Movable Type. The implementation is easy thanks to HTML::TreeBuilder::XPath. However the problem is that not too many OpenID endpoints actually has hCard. Among the four I listed above, Hatena's page is the only page which has some information ( username and userpic ). Hatena's, however, is not marked as hCard.
Now I'm wondering, if the idea of hAvatar is really valid in practice. Should OpenID endpoint have more information about who the OpenID actually is, when it is simply retrieved via HTTP GET? Or, in more REST-y sense, what resource should OpenID URL represent? And how?
社内IRCで流れてたこのリンクで初めて知ったんだけど、YouTubeからXML-RPCでブログ記事を投稿できるんですね。さっそくチェック！と思って行ってみたら、WordPress self-hostedとかいう世界的にもマイナーな項目は選べるのに、超メジャーなMovable Typeがない！ありえへんぞ！
そういうわけで、大多数を占めるMTユーザーは以下の方法でYouTube動画を自分のブログに貼れますので、ご連絡まで。
Snowy day in Tokyo allowed me to get away from family jobs and fun hacking hours. So, I tried to implement the idea of hAvatar which was first introduced in the context of WordPress plugin, for Movable Type 4. The result was however not satisfiable.
No webpage that was supposed to be my own profile documents that had hCard in it had two or more hCards in the same document. Therefore, the code must determine which hCard is actually about myself. Microformat team has already discussed about the issue and had proposed a way to find representative hCard of the page.
The only webpage that was close to the spec, however, was Twitter's. And no other websites allowed my code to find my own hCard among other hCards. My code could actually find the repesentative hCard in Twitter's, but it does not have "photo" property. Sigh.
「ほげほげな機能をMTに付けてください」みたいなフィードバックを"apache@localhost.localdomain"なんてわざわざ入力してSubmitされてもよ、別にそれほど本気で求めているわけじゃないんだな、としか思えねーよ。悪いな、他を当たってくれや。あんた、apacheのなんなのさ。
