We're definitely considering that, but we don't want to be just another enterprise LDAP vendor. What would be the unique selling point, in that case? Elasticity?

The Platform as a Service angle is very interesting, and we're planning to release an addon for the major platforms such as Heroku, GAE, OpenShift, and CloudStack. CloudStack is already setting a precedent with their new LDAP authentication functionality. We'll see if it catches on.

Thanks Steve, appreciate your feedback. You're right, data and system availability are primary concerns, and ldap.io is designed with those factors in mind.

In the event of networking or connectivity problems -- for example, if your Internet link goes down -- we're considering providing an on-premise virtual appliance configured to automatically replicate with the hosted servers. It would be very low maintenance and a good option for BCP.

For the authentication issue in general, consider the current trend of Identity as a Service and Single Sign-on as a Service -- Okta, OneLogin, and Ping, to name a few. If you use ldap.io for authentication, it would be in the same category of services, and you would also have more control of the data layer.

Along the same lines, Microsoft is now offering Active Directory for Windows Azure, to cater for similar use cases in the Windows world. See http://www.windowsazure.com/en-us/services/active-directory/

In any case, totally understand your concerns, and it makes sense to use the service for non critical purposes, in the first instance.

Kerberos wasn't planned, but we'll definitely consider it if sufficient interest is shown.

You do 389 Directory server, I was just thinking of http://freeipa.org

Looks like a cool project, will check it out.

At the moment, ldap.io is intended as more of a general purpose infrastructure service, rather than strictly identity or authentication.

You can also poke around the file system with a combination of :cd and :Explore

:dir doesn't seem to work.

This could be because :dir is not a vim command.

Yeah?

:e /etc/passwd

It's read only, but still, omgwtf.

Funny, I wrote a plugin earlier this year and came up with the exact same name. I never had time to polish and release it, but if you're interested, here's the source on GitHub:

https://github.com/mbadran/vimroom

The feature sets are different, from what I can tell.

Why?

Interesting choice of words: "sunset" instead of, say, "shut down". It's clearly a weasel word, and using a noun as a verb makes it all the more jarring.

Say what you mean, Yahoo.

For the downvoters:

Weasel words may be used to detract from an uncomfortable fact, such as the act of firing staff. By replacing "firing staff" with "headcount reduction", one may soften meaning."

http://en.wikipedia.org/wiki/Weasel_word#In_business