4 ms·

Maybe instead of overloading the shorthand with two definitions, it's best to just use the actual words.

• steve_adams_86 2y ago
  I agree. I feel like this is trying to simplify something that can’t be simplified so easily, and perhaps shouldn’t be. The desire to reduce such a complex and broad problem space suggests to me a lack of understanding of what a simplification entails. Using these different words may only present confusion in other directions. Login isn’t always what authentication is about. In fact, I recently wrote an authentication layer for identifying users based on something that would have been sent to their email, but they don’t exist as users in the system yet. They can’t log in. They don’t even need to in order to utilize this authentication layer. So it isn’t login, yet it’s a form of authentication. Permissions is a good word I guess, but it’s as specific as authorization. Why change it? Maybe I like auth because it’s familiar. I am open to new ideas though. This one just doesn’t seem to make sense.
  • danielmarkbruce 2y ago
    100%. The problem with an issue like this is that there are people who work in the field and know how complex it is and know all the terms and know no matter what terms you try to boil it down to there will be confusion because you simply cannot properly represent so much stuff in two words, let alone one. Then there are people who sort of work around the edges of such systems but don't really see how complex it is and hence come up with superficially sensible sounding things that will just cause confusion in some other way.