<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 01/27/2009 04:00 AM, Chris Messina:
<blockquote
cite="mid:1bc4603e0901261800l18b46b0dg1c682c977556649e@mail.gmail.com"
type="cite"><br>
<div>While there's cause to provide support to members having trouble
signing in to the site, I don't think we need to make major
modifications to our current approach if it is generally accessible and
workable for 90%+ of the membership.</div>
</blockquote>
Weeeell....before that it worked for 98% very well. RPX was added only
late into voting for the board. I certainly want to access the
membership account again. Besides that I don't want to store my access
records with a third party and have cookies splashed all over sites
which are none of their business really. And at last, with all due
respect, but RPX is a specific product, not plain down-to-earth OpenID.<br>
<br>
But there are implementations which apparently work very well too. Why
not use the PHP library if Ruby has bugs?<br>
<br>
<div class="moz-signature">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td colspan="2">Regards </td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td>Signer: </td>
<td>Eddy Nigg, <a href="http://www.startcom.org">StartCom Ltd.</a></td>
</tr>
<tr>
<td>Jabber: </td>
<td><a href="xmpp:startcom@startcom.org">startcom@startcom.org</a></td>
</tr>
<tr>
<td>Blog: </td>
<td><a href="http://blog.startcom.org">Join the Revolution!</a></td>
</tr>
<tr>
<td>Phone: </td>
<td>+1.213.341.0390</td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
</tbody>
</table>
</div>
<br>
</body>
</html>