Yeah one thing is for sure, permission granted by terms of use and the like, are not realistically parsable by most users. Its sad how leaned-upon they are given that.
It seems like a well constructed runtime could encourage permissions that are right-sized, action-aligned, and even linked to specific UX components - like it could be possible to have a special runtime-compatible "Pay" button that can be included in an app, which automatically serves as proof of consent to release a credit card number.
It seems like a well constructed runtime could encourage permissions that are right-sized, action-aligned, and even linked to specific UX components - like it could be possible to have a special runtime-compatible "Pay" button that can be included in an app, which automatically serves as proof of consent to release a credit card number.