<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
SitG Admin wrote:
<blockquote cite="mid:f06110401c4e50f6acb7a@%5B192.168.0.2%5D"
type="cite">
<blockquote type="cite">
<pre wrap="">I daresay your concerns are completely valid (except that 512 bytes
* 2000 users = 1 MB, != 1GB).
</pre>
</blockquote>
<pre wrap=""><!---->
I've said this before, but I suck at math :)
</pre>
<blockquote type="cite">
<pre wrap="">A standard policy web email services employ is "if you don't stop by
once in six months, your account is deleted". You could perhaps do
the same.
</pre>
</blockquote>
<pre wrap=""><!---->
Another area where I strive for (yet fail to reach) perfection in my code ;)
Perhaps "if you don't stop by in 6 months, maintenance routines will
check your site to see if it's still up, and if there isn't an active
URI there anymore, your account will be presumed unrenewable and
removed", with several checks occurring over a period of a month just
to be sure the site wasn't suffering some downtime, before giving up
on it. (Or much sooner if the *site* was up but *that URI* wasn't
around anymore.) Not sure how this would interact with URI's that the
site would normally identify with generation fragments, though.
</pre>
</blockquote>
<blockquote cite="mid:f06110401c4e50f6acb7a@%5B192.168.0.2%5D"
type="cite">
<pre wrap="">
Come to think of it, how do generation fragments work on sites that
aren't offering OpenID to all their users, but where the individual
users are just adding their own OpenID headers to each page? How does
an OP determine that <a class="moz-txt-link-abbreviated" href="http://www.somehost.com/user">www.somehost.com/user</a> is a different user than
it was 2 months ago, when the site permits someone else to recreate
with the same name so soon after deletion? I guess that would go into
an "OP best practices" list, to be careful about giving the same
generational identifier to someone who has to reset their account
with the OP using nothing more than "I have this URI *now*." (though
what being careful would *mean* in this context, I have no idea).
</pre>
</blockquote>
<br>
If we had an OP (and RP) best practices document, it would be good to
have a generally understood limit of 6 months (or whatever) so that we
can safely recycle URIs. Especially for sites such as Blogger, where
the URIs may or may not have been actually used as OpenIDs, it'd be
good to have a well understood freshness limit. (We'll use generation
fragments of course when moving to 2.0... but there are other reasons
not to recycle as these URIs are more than just OpenID identifiers.)<br>
<br>
<blockquote cite="mid:f06110401c4e50f6acb7a@%5B192.168.0.2%5D"
type="cite">
<pre wrap="">
-Shade
_______________________________________________
general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:general@openid.net">general@openid.net</a>
<a class="moz-txt-link-freetext" href="http://openid.net/mailman/listinfo/general">http://openid.net/mailman/listinfo/general</a>
</pre>
</blockquote>
<br>
</body>
</html>