4 ms·
Naming an Executor on one's will is standard but the responsibilities balloon when one expands the role to cover digital assets. My password manager contains o
by pards 5y ago
Naming an Executor on one's will is standard but the responsibilities balloon when one expands the role to cover digital assets.
My password manager contains over 400 entries. Going through each one and requesting account closures from each individual site would take years.
I don't want to burden my loved ones with that chore.
- nonrandomstring 5y agoI understand. A dead man's handle seems to be what you're looking for. You want a cron script on a well secured VPS that will de-alloc and garbage collect your whole life if you don't check in every month or so.
- pards 5y agoYes, this is what it amounts to. Maybe Europe's "right to be forgotten" laws will make this easier to automate in the future.
- nonrandomstring 5y agoAgreed. You'd definitely need some prescribed technical measures that only strong laws could enact. The stumbling block would always be that what you want is a "Delete it all, right now, and don't argue" remote API call. No commercial provider will ever give you this at present. Practically every line of code running online services is designed to avoid that and do the exact opposite. The only practical solution I can see is that you somehow obtain a certificate that allows that capability and keep it _very_ _safe_. Nonetheless, there will be some people who let their "digital self-destruct" cert get loose and then complain when a prankster deletes them. This problem adds weight to the idea that it's better to manage your own digital affairs, then it's as simple as @monthly "if [ ! -f "$STILLALIVE" ]; then ssh me@myhost find ~ -type f -exec shred {} +; fi"