4 ms·
The frustrating thing to me about current sharing/observing of data is that everything is a “trapdoor”: if your data leaks out, there is probably no way to rega
by makecheck 10y ago
The frustrating thing to me about current sharing/observing of data is that everything is a “trapdoor”: if your data leaks out, there is probably no way to regain control (“privacy panels” are nothing but a feel-good measure that still depends a lot on bug-free software and the goodwill of others). You only need to fail to protect your privacy once, and after that it almost doesn’t matter what you do.
We must rethink infrastructure to the point where the only data that we transmit is data that is inherently useless after a time. If I do something like revoke my key, it should be impossible for anyone to further use that data. Expiration dates should be baked directly into protocols so that revocation of keys and expiration are the same thing: either I revoke my key myself, or my software revokes it for me but no one else (and their buggy or insidious software) gets to decide how to respect the expiration time.
- pdkl95 10y agoWhat we need to do is build a Ulysses pact[1] into the infrastructure. This worked for a while with the w3c regarding patents. I highly recommend watching Cory Doctorow's (very) recent talk[2] on this idea, where he observes that engineers are vulnerable to incremental corruption of principles. [1] An agreement, contract, or bylaw that prohibits some type of action (e.g. a union negotiator who's payment and continued employment is contingent on never negotiation away the pension). [2] https://www.youtube.com/watch?v=zlN6wjeCJYk https://www.youtube.com/watch?v=zlN6wjeCJYk