Exploitify

by Darius Kazemi on May 6, 2011

in activism,project,projects

I was inspired by Ian Bogost’s article proclaiming that we should refer to “gamification” as “exploitationware” from here on out. I created a Chrome extension called Exploitify that replaces “gamification” with “exploitationware”, “gamify” with “exploit”, and “gamifies” with “exploits”.

This extension breaks shit — in particular, URLs on pages that contain one of the keywords will go to a dead link, since it’ll try to send you to “gamifies.html” instead of “exploits.html”, for example. But hey, I made this in 45 minutes on my lunch break today, and it’s my first Chrome extension. It’s still fun to install and browse stuff for a little while.

Click here to install Exploitify in Chrome.

{ 7 comments }

Zack Hiwiller May 6, 2011 at 12:55 pm

Wow, that’s a powerful extension, seeing as I’m on Safari, haven’t installed it and your page says:

we should refer to “exploitationware” as “exploitationware” from here on out. I created a Chrome extension called Exploitify that replaces “exploitationware” with “exploitationware”, “exploit” with “exploit”, and “exploits” with “exploits”.

:-)

Darius Kazemi May 6, 2011 at 12:57 pm

Oops. FIXED :)

Dan Silvers May 6, 2011 at 2:52 pm

Actually that gives me a really good idea. A tautology extension, wherein every word on a webpage is replaced with itself. So in the end you get the same website but it took twice as long to load.

Adam Loving May 6, 2011 at 4:44 pm

I read that there are 4 types of gamers. Achievers, Socializers, Explorers, and Killers (http://en.wikipedia.org/wiki/Bartle_Test). It seems to me you are a killer. “These gamers love to sow destruction…”

Nathan Lands May 6, 2011 at 5:09 pm

Wow, it works! Thanks.

Ben Abraham May 14, 2011 at 5:33 am

Hey Darius, I love this extension buuuuuut…

I’ve had it installed for a few days now (I use RockMelt, based on Chromium) and lately it’s been monkeying with some page elements. Stuff just wasn’t loading properly, so Iunno, probably not worth fixing but I thought it might be worth adding a warning that it might not be compatible with Chromium based browsers. Or it could have been a coincidence, but disabling the plugin did seem to fix the problems…

Darius Kazemi May 14, 2011 at 12:33 pm

It’s broke as hell, but I should have some time to fix it next week!

Comments on this entry are closed.

{ 1 trackback }

Previous post:

Next post: