gwern comments on Open thread, Feb. 9 - Feb. 15, 2015 - Less Wrong Discussion
You are viewing a comment permalink. View the original post to see all comments and the full post content.
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (321)
There are always edge-cases. A simple version of my solution can be coded up and fully implemented in an hour or less by a normal programmer (the hardest part is writing the SQL line for pulling out URLs from Firefox); the full version (a bot or daemon) could probably be done in only a few hours more.
Your desired solution, on the other hand, requires intimate familiarity with browser extensions and internals (if you want to save dynamic content and fancy things like Javascript-based chats, so much for trying to leverage existing solutions like the Mozilla Archive Format extension!).
Pareto.
My understanding is that in all cases, these deletions are really more 'marking private', and if it's done via robots.txt, well, one day that robots.txt may be gone.
Note the on-demand archiving services used by my archive bot, discussed in my page...
I'm not sure. It's possible that the packets have timestamps, but the encrypted content does not, in which case you don't get provable timestamping: the HTTPS encryption can be verified, but one could have modified the packets to read any timestamps one pleases because they're 'around' the encryption, not 'in' it. If it does, then maybe you don't need explicit trusted timestamping, but if it doesn't (or you want to work with any other data sources which don't luckily have timestamps built in just right) then the Bitcoin solution would work.
Now who's satisficing.
I would consider it, but I would be somewhat reluctant to switch because I wouldn't trust the tool to not break horribly at some point.