9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9grid.us
Date: Wed, 25 May 2005 08:11:17 +0200	[thread overview]
Message-ID: <dbde0756e4aa0dcbe04286ed487a7c28@proxima.alt.za> (raw)
In-Reply-To: <ee9e417a05052422323494918b@mail.gmail.com>

> For something
> like a 9grid, maybe you're willing to give that up in order to
> avoid creating accounts explicitly.

The accounts exist once they are used, so I think the implicit
creation is not likely to be entirely transparent.  One could consider
ephemeral userids and arrange the dump accordingly, but I think most
9grid users would prefer to have at least some permanent resources.
But maybe that's not even a requirement.  Expiry certainly would be
nice, specially to prevent denials of service.  I guess the problem is
not a new one.

In general, in a promiscuous environment, I tend to think that mapping
convenient handles to obscene^H^H^Hure userids is preferable to the
contention involved.  But one would need a proper "retirement"
procedure to free a name, which I seem to recall is part of the fossil
implementation.  After all, if boyd maps to mxyzptlk, it would
probably suffice to rename it !mxyzptlk to be sure no one acquires it
once it's retired, specially if the internal name is not readily
visible beyond the boundaries of the server.

I guess someone had better write some code, now.  It won't be me in
the immediate future, Russ, but you've certainly been extremely
helpful and encouraging.

++L

PS: Silly me, I keep thinking about issuing 9grid X.509 certificates,
but I'm loath to mention it.



  reply	other threads:[~2005-05-25  6:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25  4:39 YAMANASHI Takeshi
2005-05-25  4:54 ` Russ Cox
2005-05-25  5:20   ` Lucio De Re
     [not found]   ` <1c63862e8858694ce3b83f5d372ad789@proxima.alt.za>
2005-05-25  5:32     ` Russ Cox
2005-05-25  6:11       ` Lucio De Re [this message]
2005-05-25  6:09         ` Russ Cox
2005-05-25  6:27           ` Lucio De Re
2005-05-25  6:28       ` Lucio De Re
2005-05-25  9:04         ` C H Forsyth
2005-05-25  9:32           ` Lucio De Re
  -- strict thread matches above, loose matches on Subject: below --
2005-05-25  7:26 YAMANASHI Takeshi
2005-05-25  6:34 YAMANASHI Takeshi
2005-05-25  6:56 ` Lucio De Re
2005-05-25  2:33 YAMANASHI Takeshi
2005-05-25  2:39 ` Russ Cox
2005-05-25  1:52 YAMANASHI Takeshi
2005-05-25  2:02 ` Eric Van Hensbergen
     [not found] <237c0daf7d8dd5561cf95744c7516fd0@orthanc.cc.titech.ac.jp>
2005-05-24 12:56 ` Eric Van Hensbergen
2005-05-22 17:14 Eric Van Hensbergen
2005-05-22 17:21 ` Russ Cox
2005-05-23 14:03   ` Eric Van Hensbergen
2005-05-24  8:13     ` Richard Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dbde0756e4aa0dcbe04286ed487a7c28@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).