I was working for a company recently and we were exploring how to model what a minor can do with their guardian managed account.
I did initially look at RBAC frameworks but since it was too complex for a small greenfield project I went with one or more accounts linked to a user's profile with a RBAC junction table linking account and profile ID in a relational database.
The junction table was the secret sauce, it allows you to stuff the RBAC permissions into its rows.
I could get very far with this model. For example it allows for example who can pay for features(guardian not minor). Have multiple people manage a minor. Validate permissions for a logged in account.
is commenting on HN your job? neither is that guy. None of us here signed any style guide and get paid for sharing insight so it's more like "take it or leave it"
No it's more like everyone is free to share knowledge however they want or not share at all and so we should be thankful for knowledge not look gift horse in the mouth and police writing style
You have conflated "policing" with "commenting", at least for those you disagree with, thus contradicting your point. If I had the power to police such things I would but I can't, I can only comment and freely share knowledge on clear writing. Don't look a gift horse in the mouth ;-)
I did initially look at RBAC frameworks but since it was too complex for a small greenfield project I went with one or more accounts linked to a user's profile with a RBAC junction table linking account and profile ID in a relational database.
The junction table was the secret sauce, it allows you to stuff the RBAC permissions into its rows.
I could get very far with this model. For example it allows for example who can pay for features(guardian not minor). Have multiple people manage a minor. Validate permissions for a logged in account.