Hacker News new | past | comments | ask | show | jobs | submit login

One option could have been to use top-level domains for a team (e.g. add a TXT record to prove ownership of 'example.com' and then you can create that the 'example.com' team).

Out of interest, is there a reason you didn't go for that? Would be easy to memorise and validate while also ensuring uniqueness. Feels like it could also play in quite nicely with letting people on-board — e.g. you could have a feature that anyone with an email address in my domain is allowed to join the main team without needing admin approval.

That said, this sounds great — can't wait to try it out :)




Potentially, they could still roll this out, because a dot, ".", is currently not an allowed character in a team name.


That's because it's used to designate sub-team (e.g. companyname.infosec is a sub-team to companyname)




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: