Making sure that the financial needs of your loved ones are met if you do depart in a sudden manner, is the most selfless thing you can do. It has nothing to do about making you feel happy, it has everything to do with being pragmatic so that they have one less thing to worry about.
Every Saturday, I would step out to do grocery at 10:00am and tune into 88.5FM KQED which would be playing 'Car Talk'. I instantly warmed to the humor and banter the hosts expressed. They were top notch diagnostics as well. No doubt about it, Tom will be deeply missed. RIP.
I think what I really miss is reading web pages which were truly written from the heart. I remember even as far as back in 2005, for a search like "unrequited love", Google's top hit would be a link to a physics Phd's home page who had written about his multiple experiences of being declared 'just a friend' and how to get past being rejected over and over again.
Jump to today and the Google search yields following the obvious wikipedia link, is a whole bunch of wikihow, nytimes, urban dictionary and youtube links.
Those personal web pages with an intellectually rich content have just been lost to the dark internet.
If you want coverage, generate a few hundred thousand SHA1 hashes along with your password.
Actually, running a trickle query of random SHA1 hashes from your box might be a fun exercise, along with a trickle query of random word tuples (bonus points for using Markov chains to generate statistically probable tuples).
If you search for 'sha1 foo', that's being sent across the network to DDG's servers. And sure, if you're using SSL then it's not going across in plain text, but it's decrypted and handled on their servers in plain text; it'll probably even end up in logs and/or tracking databases somewhere. You're giving DDG your password.
At worst you're giving the attacker a hash target to try brunting. He still has to brute it, and that takes time. Select your plaintext from a large enough keyspace and it's astronomical time.
I'll need to review their policy more closely, but DDG claim fairly minimal tracking. At best someone might be able to correlate hash lookup with some IP space. That's a long way from handing over passwords. And as I already indicated, you could cradled the queries to make the search space much larger.
No, no, no. You're 100% completely misunderstanding this.
When you search for 'sha1 foo', that query ("sha1 foo") goes up to the server. They know your password is "foo" and that you're attempting to "sha1" it. They don't have a hash, they take that data and perform the hash, then send that down to you.