Semi-technical thoughts

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 So, I've generated a new GPG keypair. It has a set of subkeys (one per usage), which, theoretically, should make it all more convenient and secure. Also it uses currently-recommended algorithms (4096-bit key RSA and SHA512) and was generated using my new hardware entropy source which was the main reason for this change. The old key will be expired in a couple months unless I revoke it as superseded first. There is no reason to believe it was compromised or anything. New key's fingerprint is F819 3F12 6021 6B7D D53B 959F E273 25A3 92D7 0FFB for copying and pasting: 0xF8193F1260216B7DD53B959FE27325A392D70FFB ), long key id is 0xE27325A392D70FFB. Please import my new public key from the keyserver you prefer or using PKA dns records. You can use this command on most platforms: gpg --search-keys 0xE27325A392D70FFB (Unfortunately, GnuPG or/and keyservers don't really support search by fingerprint or showing it in the imp...

Some of my 3.5 loyal readers might see themselves to this new domain sometime next week when they care to come here. What is this? Have I gone all corporate and will start to earn money on this somehow? I wish, bro. No, I just saw this domain in the expiring list yesterday and thought that it could fit my blog nicely and I never liked 3rd-level domains. The only reason I ever had a blog not on a custom domain is that I wasn't sure whether I'd be able to write more than a couple posts. It appears I was, after all, even though this is neither the most actively updated nor the most popular blog, so it's time to personalize it and make it possible to become google-independent one day if I ever want to. As with everything else, custom domain is the way to be independent from any particular provider. It's true for blogs, it's true for email (I'm one of those who do have custom-domain emails yet are too lazy to migrate from gmail completely). I'm not likely t...