3 ms·
But capabilities are not good or bad, no more so than e.g. integers. What the post talks about is "a good system" of capabilities, that is, a comprehensive, lo
by nine_k 3y ago
But capabilities are not good or bad, no more so than e.g. integers.
What the post talks about is "a good system" of capabilities, that is, a comprehensive, logically sound, lean way to describe capabilities that would be widely accepted and applied. With that, indeed a lot could be achieved.
- spaceribs 3y agoI think you can already see the issue with that proposition in terms of Google's attempts to prevent ad-blocking in MV3. Google went so far as to design a brand new protocol for handling web requests in such a way as to make it difficult or impossible to do proper blocking. They "Reworded" the capability. If we assume that the "owner" of this list of capabilities is the same party that's writing the software, you better believe they don't (or won't eventually) have the user's needs in mind. Enshittification makes a fool of us all.
- marcus_holmes 3y agoWe've seen this elsewhere. "Security" becomes not about protecting the user's data from malicious operators, but protecting the manufacturer's data from the user. If we do agree a standard it'll need to be about actually protecting the user, but implemented by manufacturers who have no incentive to actually do that, and lots of incentive to protect their data, sorry, business model.