Contact Me🔗

Please feel free to reach out to me! The easiest way to do that is online.

I'm am physically based out of San Francisco, CA, but am also frequently in Oaxaca, MX. I'm always happy to meet up for coffee or go for a hike, so drop me a line if you know any good spots. ☕⛰️

👋🏼 Recruiters 💁‍ (please read) 👀🔗

If you're looking to contact me about a job opportunity, thank you!!! I just kindly request that you don't use my personal email address directly, but rather start by contacting me through this recruiting form I have set up. I promise that I will get back to you within a day or two.

Personal Contact🔗

Keybase-@asimpletune

Twitter-@asimpletune

GitHub-@asimpletune

Hacker News-@asimpletune

[email protected]

Professional Contact🔗

For professional opportunities, please use my dedicated form. This helps greatly in making sure I can respond quickly, and it helps me organize the information you have by storing it a uniform format. It takes about 30 seconds to fill out, and you will receive a confirmation message that it worked.

PGP Key🔗

If you need to send me something securely and don't have keybase (or you don't want to use it), you can send me encrypted content, or verify content signed with my signature, directly, using my public pgp key.

My full key ID is C6660576BF3C511FC28CBB7A9136560AE0E8A625
In fingerprint form it is C666 0576 BF3C 511F C28C BB7A 9136 560A E0E8 A625
It's shortened (64 bit) version is 9136560AE0E8A625

(Note: you can verify my public key by checking the DNS record I have associated with it)

dig +short contact._pka.spenc.es. TXT

You should see the same fingerprint as above, along with a link to my ascii public key, encoded in the response.

"v=pka1;fpr=C6660576BF3C511FC28CBB7A9136560AE0E8A625;uri=https://spenc.es/pgp/pubkey.asc.txt"

How To Send Me an Encrypted Message🔗

If you want to send me a message, e.g. hello.txt, that only I can read, take the following steps:

Import my public key, using its key ID (The shorter, 64 bit version is ok)

gpg --keyserver pgp.mit.edu --recv 9136560AE0E8A625

Encrypt your message with me as a recipient

gpg --encrypt --armor --recipient 9136560AE0E8A625 hello.txt

A new, encrypted file will be created, ending in .asc. For example, hello.txt.asc would look like this:

Send me the message

You can attach it in an email or just copy and paste the file created from step #2 directly in the email body.

How To Verify Content Signed with My Signature🔗

If someone sends you something claiming it's from me, you can verify that I really sent it using the command line tool gpg to check the message with my digital signature. For example, if you receive a signed message named hello.txt.asc, claiming to be from me, you can verify the signature used to make the message and compare it my own.

Here's an example signed message, e.g. hello.txt.asc:

You can verify that I indeed really did send it by following the following steps:

Import my public key, using its key ID (shorter, 64 bit version is ok)

gpg --keyserver pgp.mit.edu --recv 9136560AE0E8A625

Verify the message

gpg --verify hello.txt.asc

You will then see a message that looks somewhat like this:

gpg: Signature made Fri Oct 15 12:03:44 2021 CDT
gpg:                using EDDSA key C6660576BF3C511FC28CBB7A9136560AE0E8A625
gpg:                issuer "[email protected]"
gpg: Good signature from "Spencer Scorcelletti [email protected]>" [ultimate]
gpg: WARNING: not a detached signature; file 'hello.txt' was NOT verified!

☑️ Make sure that the key ID there 👆 matches mine: C6660576BF3C511FC28CBB7A9136560AE0E8A625