I have thought about this and will probably do so. I was just hoping
it would be easy to just add an additional namespace. Seems cleaner to
me.
On May 20, 11:46 am, Andy Mikhailenko wrote:
> What about using emails or openIDs for authentication? These include
> namespaces per se ;)
>
> On May 20
What about using emails or openIDs for authentication? These include
namespaces per se ;)
On May 20, 1:09 am, Timboy wrote:
> Initially we will have in the ballpark of 10,000 Private users. Anyone
> have an idea on an additional user namespace?
>
> On May 19, 8:42 am, Aneesh wrote:
>
> > How ma
Initially we will have in the ballpark of 10,000 Private users. Anyone
have an idea on an additional user namespace?
On May 19, 8:42 am, Aneesh wrote:
> How many private users do you have? If it's just a small number,
> consider using the same model for all Users, and making some profiles
> p
How many private users do you have? If it's just a small number,
consider using the same model for all Users, and making some profiles
public/private. A couple usernames will be taken, but that shouldn't
be a big deal.
If you actually want a second namespace, I'm not sure of the best way
to pro
4 matches
Mail list logo
