I’m not a lady easily upset by the silly things that happen in male-dominated cultures. When I went on stage to speak at DEFCON 19 a series of events escalated to a portion of the audience shouting for me to take my shirt off. While I was a little sad that conference security had no idea how to de-escalate that (I sure hope they teach them now) and I had to do it myself, it isn’t fair to hold a whole conference, much less a whole culture accountable for the actions of about 2-dozen piss-drunk semi-asshole dudes who thought they were “just being funny.” I was proud to speak at DEFCON 20 as a member of a community I dearly love, and I plan to apply to speak at DEFCON 21.
Yesterday was my first time at GDC, and for the first time I felt really uncomfortable at a conference. It wasn’t that anybody was being unkind, it was a simple numbers game. We all know there aren’t many lady developers, especially in video games. There are, however, a lot of companies that have hired women who are pretty but not models, dressed in normal street clothes to push whatever product they have. Products range from energy drinks to some developer program to help market your app. This meant that when you first met a girl, it was statistically safe to assume she was not technical and just there to push something. This assumption was remarkably hard to break. When trying to join lots of interesting conversations, I either had to be that asshole who casually drops her credentials, or deal with a few rounds of being told things were “complicated engineering stuff.”
Eventually, I found it socially easier to introduce myself as a tag-along to my boyfriend than to try to break my own path, and wound up spending most of the day either stuck to his side as my “see? I’m not here to be evil” mascot or walking around with other dudes. It was incredibly depressing. I met some really wonderful people in the game community who accepted me for who I am and who I am sure I’ll be friends with for a long time, but the overall atmosphere was very grim, and I was a little relieved to go home.
The only reason I find this to be worth bringing up is because even my extraordinarily egalitarian boyfriend didn’t quite see my plight until I explained it. He commented a few times on how few “booth babes” there were, only counting the ones who posed in bikinis with men holding plastic swords in photographs, and thought it was a great sign of progress. Me? I found them way easier to deal with than their plain-clothes counterparts. I’m not a model, nor was I dressed in stilettos and a bikini, so nobody would ever mistake me for being one of them. It was their plain-clothes fairly-ordinary-looking counterparts that made my life hard. Goodness knows, if I had the power to bring tons of other technical women at the conference that would be an optimal solution but barring that, selfish as it may sound, if I could have substituted all the plain-clothes promoters for traditional booth babes, I would have done it in a heartbeat. Then I’d be free to have a great time being what I normally am at conferences: a curiosity, an anomaly, and an excitable nerd.
In early 2012 a hackerspace with the words Hacker and Dojo that I don’t want getting SEO linked to these images was having a lot of trouble with a series of news articles using the Dojo logo to round out any generic article about “bad guy hackers.” Sending take down notes was getting tiresome, and so one day a gentleman named Joel had an idea.
Perhaps we could make a “press” page where we could provide some guidance on how to learn more about “hackers” and “hacking” as well as provide images they can use for their articles. “Are you looking for an image of a badguy hacker? … Well, we aren’t really about that but here are some images you could use to convey that, I guess” – for extra points we’d sneak jokes into those images, for example, the “badguy hacker” could be using a keyboard plugged into a Nintendo, or they could be playing a video game that looks like “hacking”, or watching “The Net” and taking notes.
So I went to the pharmacist today. Pharmacist rang up my medicine and, with insurance, it came to be about $430. Due to previous paperwork fail I have been unable to get my medicine for over a week and me walking away without my medicine is medically inadvisable. My pharmacist knows this.
Me: What is this? Did you get my new insurance? Did my new insurance raise the price?
Pharmacist: Maybe you have a deductible to meet?
Me: Yeah, but I use to buy this medicine without the insurance and it was $210. Why is it more expensive now? Can I read the bag? [reads] Yeah nothing has changed except now you’re giving me 60 30mg pills instead of 30 60mg pills.
Pharmacist: 60 pills is different than 30 pills
Me: Not when you’re prescribed two a day and because they are half as strong. If it is the same to you though, can you give me 30 60mg pills?
Pharmacist: We would have to redo all the paperwork with your doctor. Would you be willing to wait another week?
Me: Why is it so much more expensive to get double the half-sized pills then?
Pharmacist: We had to package them in two bottles.
I recently transferred a relatively large sum of money on PayPal. Concerned about fraudulent activity, PayPal challenged me to answer a phone call and enter a code.
Awesome idea right? There’s just one problem: the page prior to this invites me to update my phone number and requires no verification at all. I took the liberty of adding a phone number this PayPal account has never heard of.
So thank you PayPal, for protecting me against terrorists and account hijackers who don’t have phones.
12VDC Power Supply, 1.0A (salvaged from that box of power cords whose owners you no longer know)
cheap old APC UPS (provide 12+hr battery backup)
2 1N4004 diodes
Serial cable you don’t mind cutting up
nMOSFET (we used irf732)
Here are the steps for building the controller board
Building the Controller Board
Cut off one end of the serial cable. Find the ground and pin 4 wires, and tuck the rest back
On the breadboard, wire up the maglock controller board according to this schematic
Get an orphaned DC power converter to some electronic device you no longer use. Check it is 12V, and probably 1.0A. Cut off the end of the power adapter, and figure out which end is positive and which one is negative. This is your power supply for the maglock circuit. Plug it into the breadboard.
Mounting the Hardware
Mount the maglock on the door according to the instructions, but don’t set up the power cords permanently yet.
Put the big button in one of the project boxes and wire it in series so that when it is pressed it opens the power circuit to the maglock. This is how people will leave from the inside of the door.
Mount the knife switch on the wall in series with the maglock and button so that when it is open it cuts the power to the button and maglock. This is how you activate and deactivate the maglock.
Add the relay on the controller board in series to the maglock power circuit, so it can control the whole thing.
Plug the other end of the controller board serial port into your junky computer
Plug the USB RFID reader into your junky computer
Plug all of the power sources into the UPS
Setting up the computer
If you are using the same RFID readers we use, they only work reliably with FreeBSD and Windows. Our code works with Linux/FreeBSD. Install FreeBSD from http://www.freebsd.org/
Your maglock controller board is connected to Pin 4 of your serial port. Pin 4 is RTS, a feature generally considered to be out of date and no longer used in most RS232 communications. It expresses that your computer is ready to recieve data. We are going to write code which will flip this pin high and low, and thereby let you control the maglock circuit.
Please note that in this code the file which pyserial is opening may not be the right file on your system. Your device will be in the /dev/ folder for Linux and FreeBSD. If you are using a USB to serial converter, look for a USB device. When you find the file of your device, change the file name in the code accordingly.