Weitere Ă€hnliche Inhalte Ăhnlich wie Implications Of OpenID (Google Tech Talk) (20) Mehr von Simon Willison (20) KĂŒrzlich hochgeladen (20) Implications Of OpenID (Google Tech Talk)27. Yes, but you donât need
to ask their permission
to implement it 35. If you have the ability to
run your own server
software, you can do it
for yourself. 42. So my users donât
have to sign up for an
account? 56. How can I tell if theyâre
an evil spambot? 80. Users can give away
their passwords today -
this is just the OpenID
equivalent 96. If an OpenID is just a URL, is
there anything else interesting
you can do with it? 99. An OpenID from
sun.com proves that
someone is a current
Sun employee 104. Why is OpenID worth
implementing over all the
other identity standards? 111. âI forgot my passwordâ
means your e-mail
account is already an
SSO mechanism 115. I can has lolcats!? BETA
Make your own lolcats! lol
Sign in with your OpenID:
OpenID: Sign in
http://icanhascheezburger.com/2007/05/16/i-has-a-backpack/ 130. âI forgot my passwordâ
becomes âI canât sign in
with my OpenIDâ 134. You can take advantage
of site-speciïŹc services
around each of their
OpenIDs 144. âPeople keep asking me to join
the LinkedIn network, but Iâm
already part of a network, itâs
called the Internet.â
Gary McGraw, via Jon Udell, via Gavin Bell 147. ... so do âforgotten
passwordâ e-mails! 148. If e-mail is secure
enough for your userâs
authentication, so is
OpenID 152. Donât publish a userâs
OpenID without making
it clear that youâre going
to do that 155. This could be built today
by sites conspiring to
share e-mail addresses 161. They will smack down
anyone else who asserts
their own patents against
OpenID