3 ms·
This was solved within corporations to an extent 50 years ago. Institutions that used IBM mainframes tend to use an id of the form aaann where a is a letter an
by emmelaich 9y ago
This was solved within corporations to an extent 50 years ago. Institutions that used IBM mainframes tend to use an id of the form aaann where a is a letter and nn a number. An example is Matthew Garret's id "mjg59". Large corps still use something similar. You can have a separate mail address and aliases but they are not your id.
- dingaling 9y agoNames changed to protect the guilty: I joined a Big Dinosaur Company early enough that they were still using mainframe RACF as the system-of-record for authentication, flowing downstream to LDAP. So indeed I received, for example, dlg28 as my ID and stem for e-mail address. However after several years the SoR was migrated to Windows LDAP ( can't remember its brand name ) and it generated 'sensible' IDs for all the newer staff. So someone received JimSmith as ID & e-mail address. We oldies felt old and uncool! So a project introduced self-selected e-mail aliases for the oldies, which then led to interpersonal conflicts because jsm22 wanted JimSmith@, but the 'new' Jim Smith already had that... But jsm22 felt he had title to it since he had worked there 40 years etc etc So he was given JimBSmith@ which of course led to misdirected e-mail. Hilarity ensued. I'd rather they had never introduced the long-form IDs at all!
- orf 9y agoInteresting story, but it seems like it's the oldies who are at fault in this tale.