Hi all, I just wanted to report a problem I had getting [piston](http://piston.readthedocs.io/en/develop/) installed on my macbook, **and how I seem to have fixed it.**

**Please Note:** I have absolutely no idea what I am doing. What I am about to describe seems to have worked for me and my computer appears to still be operational, anything you do to *your own* computer is entirely at your own risk and you need to be aware of my utter lack of expertise if you try it yourself.

### The Rig

I'm on a brand-new 12" MacBook running MacOS X El Capitan and python 3.5. I've done nothing to the computer in the way of customization; my setup is almost exactly OOTB.

### The Problem

I installed piston using `pip` following the instructions on [this page](http://piston.readthedocs.io/en/develop/installation.html) exactly. It seemed to work (after a few tries, because I inevitably ran into goofy problems with pip and had to try this and that and... you don't want to hear how I fixed that one; I probably ran `pip --upgrade` a time or too as well).

Then, I fired up python and moved on to [the testing steps on this page.](http://piston.readthedocs.io/en/develop/lib.html) As soon as I executed
`from piston.steem import Steem`,
python gave me this stupid error message that unfortunately I didn't save, but it included
`Library not loaded: libcrypto.1.0.0.dylib`
and I think the end of it was
`image not found.`

WTF???

So what do you do when you get some random error message that you don't understand at all? Well, I think the correct answer is to go find an adult who knows what's going on. **But I did what I always do: I spun the google roulette wheel and prayed that it didn't land on something that would ultimately result in the theft of my identity.**

### The Fix

Here's what the google oracle gave me: [a website claiming to have a fix, but note that the word "hacks" is in the url.](http://mithun.co/hacks/library-not-loaded-libcrypto-1-0-0-dylib-issue-in-mac/) Maybe not the best of signs? But hell if I'm going to go ask a real person for help, so let's just try it out!

**It turns out that Apple was smart enough not to let me do what this guy was suggesting.** If you follow his instructions exactly, as soon as you try to run the `sudo cp ...` command, the terminal gives you a nice error message to the effect of
`hey, wtf are you doing you n00b, you can't just write garbage into usr/lib!!!`

"What now?" I thought to myself, my despair growing ever deeper. "Back to google!" This time, I landed on a very helpful [stackoverflow article](http://stackoverflow.com/questions/32659348/operation-not-permitted-when-on-root-el-capitan-rootless-disabled), where the top-voted answer said "here's how to get around the safeguards that Apple put in place," and the 2nd-top-voted answer said "Hey! How about instead of being an idiot, you *don't* be an idiot and write to `usr/local/lib` instead?" And whammo, that's what I did.

Aren't you glad I'm this long-winded? Isn't this fun? So without further ado, here's the fix, explained in a screenshot from the hacky guy I linked to above.
Don't do what I redded-out, and DO do what I wrote in green:
https://ipfs.pics/ipfs/QmcjGy9seCYF5LZFSEfgyhwtNkWqXtxjtEzgYi6pmuSCUu

After I did this and restarted my Python kernel, I could run `from piston.steem import Steem` and **voila! No errors!**


AAAAND let's just give one more disclaimer: **I don't know why what I did worked. There's no particular reason to believe that it will work for you. For that matter, there's no particular reason to believe that you won't get your identity stolen as a result of following my hack advice.**