Archive for November, 2007

Welcome to probably the most useless blog post on the web.

Now you can happily animate stuff in the address bar (do you remember the nineties and nice status bar animations ? :) ) .

The beautiful online demo can be found here : Demo of animated address bar

HTML:
  1. <title>Totally usesless 'ajax' 'loading' image in the address bar as a spinning thing</title>
  2. <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  3. <meta name="author" content="AF83.com" />
  4. <script language="JavaScript">

JavaScript:
  1. <!--
  2. /**
  3. *  Copyright (c) 2007, AF83
  4. *  All rights reserved.
  5. *
  6. *  Redistribution and use in source and binary forms, with or without modification,
  7. *  are permitted provided that the following conditions are met:
  8. *
  9. *  1° Redistributions of source code must retain the above copyright notice,
  10. *  this list of conditions and the following disclaimer.
  11. *
  12. *  2° Redistributions in binary form must reproduce the above copyright notice,
  13. *  this list of conditions and the following disclaimer in the documentation
  14. *  and/or other materials provided with the distribution.
  15. *
  16. *  3° Neither the name of AF83 nor the names of its contributors may be used
  17. *  to endorse or promote products derived from this software without specific
  18. *  prior written permission.
  19. *  THIS SOFTWARE IS PROVIDED BY THE COMPANY AF83 AND CONTRIBUTORS "AS IS"
  20. *  AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
  21. *  THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
  22. *  PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
  23. *  CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
  24. *  EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
  25. *  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
  26. *  PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
  27. *  OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
  28. *  NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
  29. *  EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  30. *
  31. *  @copyright  2007 AF83 Ori Pekelman
  32. *  @license    BSD License (3 Clause) http://www.opensource.org/licenses/bsd-license.php
  33. *  @package    Useless Stuff
  34. */
  35. // Configure :
  36. var TextBefore=' ...  Loading ... ';
  37. // End configuration
  38. var AddressBarLoaderTimeOut;
  39. var OriginalLocationHash = document.location.hash; // so we can restore original url
  40.  
  41. function loc_hash(a){
  42.  document.location.hash =TextBefore+a;
  43. }
  44.  
  45. function spinStart(){
  46.     AddressBarLoaderTimeOut=setTimeout("spinStart()",100);
  47.     loc_hash("|");
  48.     loc_hash("/");
  49.     loc_hash("-");
  50.     loc_hash("");
  51.     loc_hash("|");
  52.     loc_hash("/");
  53.     loc_hash("-");
  54.  }
  55.  function spinStop(){
  56.      document.location.hash=OriginalLocationHash;
  57.      clearTimeout(AddressBarLoaderTimeOut) ;
  58.      }
  59. // -->

HTML:
  1. </script>
  2. </head>
  3. <h1>Totally usesless 'ajax' 'loading' image in the address bar as a spinning thing</h1>
  4. <div style="margin:100px;height:100px;width:100px; background-color:#333;font-size:18;color:white;" onclick="spinStart();">Click on me to start address bar ajax loader</div>
  5. <div style="margin:100px;height:100px;width:100px; background-color:#333;font-size:18;color:white;" onclick="spinStop();">Click on me to stop</div>
  6. </body>
  7. </html>

Click to continue reading

Voilà la présentation qui a été faite lors du ParisWeb 2007. Pas trop de texte là donc si vous n'avez pas participé vous risquez de ne pas tout comprendre...

La présentaiton -The long talk - Microformats pour le web comme plateforme de communication

Click to continue reading

OpenID

Achieving Single Sign On (SSO) in a decentralized way (anyone can be an Identity Provider) with an open technology (anyone can contributre, no patent fees) is great.

But from the enduser's perspective OpenID is nearly pointless : forms auto-filling and session cookies make sign up/in really easy.

Yet there are further rooms for OpenID to grow :

  • SSO remains a real issue on mobile devices where browsers have not yet forms auto-filling and keyboards are small.
  • OpenID is good for login in a social network ... not to access your bank account. A real and useful SSO should allow you to log in any website. A trust layer for OpenID is beeing specified trouh the PAPE Extension (Provider Authentication Policy Extension) : a website will be able to request from an OpenID provider a certain level of authentification. Here again, mobile has a role to play.

Using OpenID log in, you can transmit some data about yourself. OpenID 1.0 (through Simple Registration Extension) permits very simple data transmission (email, nickname, date of birth ...). OpenID 2.0 comes with an improved scheme : the Attribute Exchange extension. But all this implies your data are centralized within your OpenID Provider. Here is where OpenID technolgy ends : Your data is spread across multiple websites ... Other protocols are needed for you to access them all.

Portable Social Network

Not having to re-import / invite all your friends / relationships (that is your "social graph") when joining a new social network ... this concept is referred to as Social Network Portability.

Microformats provide a solution. While joining a new social network, your should be able to link to your existing pages on Facebook, LinkedIn, Twitter etc. As these pages should include microformats such as XFN "rel=friend" links any machine can parse them and find out about your friends.

Beyond relationships : Data portabilty

Friends is not just all .. From within any website you should be able to access photos from your Flickr account, contacts from your Plaxo address book, events from your Google Agenda etc.

OAuth is all about this : having a website access your data from another site .. without having to give your password away. It uses redirections allowing the user to log in anothersite, OAuth having data exchanged behind the scene.

OpenID, OAuth, Microformats : how does it fit all together ?

There is an interesting link between OpenID and Microformats : as you OpenID identity (for a given profile) falls into one single URL, it is wise to have all your links to social networks on this page (using XFN "rel=me" tags). Some OpenID providers (such as ClaimID) allow their users to do so.

OAuth and OpenID share their openess and the use of redirections. But they don't need each other. From the enduser perspective, the OAUth process can be eased if both site implement OpenID.

This is the beginning ... Many websites were supposed to implement OpenID .. but still don't. OAuth has just been released and has not been really implemented yet. Some issues have still not been addresses : data encapsulation ? GData ? what about synchronisation ?

As AF83 is concerned, we can foster this move towards fluid and open-standard based personal information transmission by allowing for OpenID sign in / up, make our web pages more semantic by using microformats and (not that easy) provide an OAuth API to our users data.

Click to continue reading

Creative Commons License
This work is licensed under a Creative Commons Attribution 2.0 License.