Hi Henry, I think you are doing a great job around here. Unfortunately, very misunderstood around here. Not that I am qualified to judge your work. My apologies!. Keep up the good work!
On Mon, Jun 7, 2010 at 11:24 PM, Story Henry <[email protected]>wrote: > > On 7 Jun 2010, at 19:11, Steven Livingstone-Perez wrote: > > > Hi Henry - Yeah - having played with FOAF+SSL it is nice, albeit a bit of > > work is needed at the moment. > > yes, it is improving all the time. We really only have proofs of concepts > for the moment, so not something that is end user ready. If the quality of > engineering of the OpenId team would help out it would be unbeatable. > > > I think for that bit to get easier we either > > need really good installers or, ideally, support by the browsers to make > the > > cert bits a no brainer. > > Did you see the video? I put it together myself, and it is my first screen > cast so it is very clumsy. But if you get over that, you will see that > creating > a certificate is a one click affair. That piece could not be easier. > http://bit.ly/axlT0s > > But yes browser manufacturers could do a little work and the core values of > the > original OpenId team at least (I have not followed the work recently) would > be > fulfilled. Firefox probably needs the most work at the UI level. But that > just requires > a bit of common sense on their part, no engineering feat. For the moment it > is useable. Chromium (Chrome developer release) now works, and Opera is > excellent. IE I think also works well (I don't have windows myself). That is > also evident from the screencast. > > > > > It is certainly the closest I have seen to OpenID just working in the > > browser. > > Thanks. > > Now the very positive thing about OpenId is that it is a very important > piece that can complement Web IDs very well. For browsers that don't support > Web IDs, Open IDs are the > next best thing. In fact I think that Open ID could use foaf+ssl to improve > its protocol, so as to close that last gap. > > I pointed out how this can be done a while ago in "Making Open ID RESTful" > http://markmail.org/message/oub3mhq4q4lpazwh > > I have updated the foaf+ssl openid section > http://esw.w3.org/Foaf%2Bssl#OpenID > > Hope that helps, > > Henry > > > > > /steven > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf Of Story Henry > > Sent: 07 June 2010 17:51 > > To: Steven Livingstone-Perez > > Cc: 'John Panzer'; 'SitG Admin'; [email protected]; > > [email protected] > > Subject: Re: [OpenID] Finally the Shit has hit the fan! > > > > > > On 7 Jun 2010, at 18:42, Steven Livingstone-Perez wrote: > > > >> The idea in principal appeals but a lot seems to be dependent on > >> browser vendor support & OpenID in the browser should really have been > >> (and should still be [1]) a no brainer for the browser vendors - I > >> anticipate the same level of "uptake" by them for this. > > > > It already works in the browser, and has for years. The problem is that > most > > people here don't want to look at the solution, because of fear of the > > semantic web it seems, or some such (not sure). > > > > You can see it working in this home made video > > > > http://www.youtube.com/watch?v=8iZPJBpI2Po&feature=player_embedded > > > > (I welcome people coming up with better videos) > > The protocol is detailed here: > > > > http://esw.w3.org/Foaf+ssl > > > > There are some small browser improvements that could be made, though it > > would not take long to convince some of the browsers vendors to make > them. > > > > Henry > > > >> > >> > >> In short, until we can get the browsers to put social as a first class > >> citizen (and look how long universal OpenSearch support in the > >> browsers > >> took) we have a battle. > > > > > > _______________________________________________ > specs mailing list > [email protected] > http://lists.openid.net/mailman/listinfo/openid-specs > -- http://hi.im/santosh
_______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
