Would it be dumb to name my Users table "Member" instead of "User"?

Will I and other devs be annoyed with me?

Values-Aligned Communities | citizen of Black Rock City

JavaScript, work at LinkedIn, building Jewelbots 

Yeah Next-auth uses User so I’m gonna keep it but alias some stuff

I don’t think they will mind. The annoying thing will be there are frameworks that map things to Users.

bc I don’t think they are “users” they are members of a community

Is there a particular reason to do this or just personal preference? If it's the latter I would rather stick to the standard (less cognitive load for maintainers of the system)

uphill battle for no big win. youll have something analogous to members and have to do new gymnastics. the hearts there, but you can surface that on the frontend in other ways

As long as you’re never ever going to have users that aren’t considered “members” 😬