Not sure what will go here yet. Maybe something. I've mostly just missed having something at this domain.
I do have a couple of posts up as well as a couple of partly completed projects. Links are in the header.
I find that most of the time, when I am forking a respository to do a pull request, I’ve already cloned the respository. I don’t do it often enough that I have it memorized, so I go looking for guides… and find that they all are for cloning a new repository, making changes, then doing the pull request. Then I go look up the actual commands that I want and proceed.
This is here for me, and, presumably, you to follow step by step those rare times that you need it.
How do you know that that person you need to message on Slack, Facebook, LinkedIn, Twitter, etc. is who they say they are? How do you know who is sending you that file and if you should trust them? How do you guarantee that the message you send is not being intercepted in transit?
By meeting in a dark alley, exchanging information that only you and the other person know, then tatooing their public key on your arm and manually typing it in to a computer that has never touched the internet, and then passing the messages onto this computer, signing (and potentially encrypting) them, and then passing them back to the internet using the IPoAC protocol.
Er, yeah, no. Well, if you have something that is that important, you know you do, and are already doing some variation of the above. If you need to get such messages to or from me, I guess you can check out my Public Key Page and we can arrange something.
For everyone else, there’s Keybase.io - Crypto for everyone!.