3 ms·
For public data I am inclined to agree with the parent. You could just pass a single auth token to the database if it supported it for public data only and fet
by publicdatamaybe 4y ago
For public data I am inclined to agree with the parent.
You could just pass a single auth token to the database if it supported it for public data only and fetch it that way. Kinda like a bearer token, etc...
Therefore having direct access to the database from the client side only for public data.
This would be very beneficial to the web as a whole as a lot of the data is public data.
Then the separation of privilege/access has to happen directly at the database level which is totally possible.
Would be a nice addition to the web to treat public data differently.
- worklikethis 4y agoAt the database table level, each field could have the following properties which processed together would decide the level of access for that piece of data stored. data_access: private|public data_scope: single|composite data_exempt: age|gender|otherpiifield Somewhat protecting PII by not allowing querries which would infringe PII rules when selecting multiple sensitive fields.