Erik Rhodes: "A Romance with Misery"

Posted on June 14, 2012 by bluedepth

When I got home from work today Scott called up from where he was enjoying the cool of the basement that Erik Rhodes had died in his sleep, of a heart attack. He was 30 years old.

Erik Rhodes, or James as his true name would turn out to be, was a adult performer and after reading his tumblr, which I linked to this post above, I noticed what anyone could. This person was very sad and in a way going to pieces. Post after post saturated with tone that was screaming out to anyone who would listen that he needed help. But nobody apparently noticed. I have to admit that I didn’t even notice myself until the blog was pointed out to me. I feel sorry for him and his family, what a loss.

Throughout all the sadness I can’t help but spy the Adonis Complex lurking in the background. All men have this darkness lurking somewhere in their psyche. Just like girls have their own self-image and self-worth issues, being razor thin and looking-near-death-is-so-hot, but the Adonis Complex is really a very male thing. It starts out when we compare ourselves against each other. This man has a full head of hair, 3% body fat, muscles galore. We feel envy, then we approach the envy in a very male way. We try to fix what is wrong with us. Some workout endlessly, struggling for a body that may always elude them while others seek shortcuts, usually one drug or another. Anything that’s a stimulant can lead to abuse of a shortcut. Sometimes it’s a naive shortcut like nicotine abuse, sometimes it’s cocaine or heroin. Sometimes it’s anabolic steroids.

The Complex is like a fog on the brain. It colors everything. Comparisons pile up on comparisons and as we start reaching our goal our self-worth and self-image can (not will) go right into the toilet. What you end up with is a beautiful specimen of masculinity that is wretchedly depressed. Once Adonis arrives, his only real destination is to drown in the pool of water that he sees his reflection in. Yes, I’m mixing my mythical metaphors, the tragedy is of Narcissus, not of Adonis, but it’s for Adonis the Complex is named after and it’s Narcissus that holds the tragedy.

Women suffer similar body-image pressures, but the genders are very different. A fish can’t teach a bird to swim and so trying to explain it to a woman is really something I’m not capable of doing. The feelings, the pressure, the drive, and above all else, the mechanical aptitude that males bring to “fix” what is wrong ends up spiraling out of control.

So we get back to this poor soul. Narcissus died of a heart attack in his sleep. They’ll find an overdose of steroids, he wrote about how that was his plan after all, and the rest of us will be left behind, some will have lost an idol, some will have lost a family member. We all will lose someone that could have been rescued if more people knew and reached out.

And then that leads to the almost obvious analysis waiting at the end of all of this. Are the people who do such things, adult entertainment, pornography, all on a path similar to the one James walked? Are these people “terminally pretty”? And then people will start to point their fingers at the porn industry itself for perpetuating mental illness, body dysmorphic disease and self-image crises that lead to self-inflicted abuse that is just a stones throw from suicide.

There is always hope, there is always someone to reach out to. Just get in a car and drive away from your pain. Walk up to a house, anywhere there are decent people and knock on their doors and tell them you need help. Good people are agents of hope. They will help, no matter who they are. That is what good people do.

Superpass Password Hasher

Posted on June 13, 2012 by bluedepth

Superpass Password Hasher.

This site has a rather novel approach to dealing with passwords. I see this a lot in both my personal and professional life, especially when people lose their computers. The question looms ‘Did you… ?” and usually the answers aren’t very good at least from a security standpoint.

One of the biggest things that people can-and-should do is keep individual passwords for every single site they access. Most people could approach this via tools like my beloved 1Password but this may be another approach that might also work. It uses an encryption staple called a hash to generate a multi-character password based on some simple password, a salt (which is used to increase the randomness that is added to the encryption routine) and the domain you are working with. It’s quite elegant in that it offsets the need to store individual passwords because it, supposedly, relies on stable domain names to provide password reproducibility. Each time you enter your simple password, and the domain name hasn’t changed, you should get the same hash over and over again. I still think that 1Password is still the best choice for everyone, but this might be a good starting place especially if cash is tight and you can’t swing a 1Password license.

UPDATE: After trying this out I discovered that it only really works well on plain sites like Google.com. If you go to any other sites, like Apple or nytimes.com the code breaks down on Safari. I couldn’t get it to even work on Firefox 13 on the Mac, so perhaps this isn’t as robust as I had hoped. The idea is still good, however. For what it’s worth.

Dell Exec: The iPad Is Too ‘Shiny’ For Business | Cult of Mac

Posted on June 12, 2012 by bluedepth

Dell Exec: The iPad Is Too ‘Shiny’ For Business | Cult of Mac.

I read this article and found myself agreeing wholeheartedly. Here where I work we’ve got many iOS devices and they are all working quite well. That Dell has the temerity to criticize iOS devices in the enterprise setting really strikes me as sour grapes that their stupid Streak tablet failed to catch hold. Then again, it was trying to use Windows on a tablet, which I can pretty much guarantee is going to flame out before it even gets going.

The article states that the fellow from Dell Australia went so far as to claim that it would put a burden on the IT infrastructure. I call bullshit on that. I’ve been working with a gaggle of iPhones and iPads and frankly, I’ve never had one person come to me seeking support for their iPads, mostly because the devices are built that well. Now perhaps they are all quietly suffering in silence, but I think it has more to do with how well the devices are constructed and how integrated the entire experience is. The hardware and the OS work so tightly with each other that there is little room for bugs to rear their ugly heads.

Gunnar Glasses

Posted on June 12, 2012 by bluedepth

About a year ago I discovered a company that made eyewear expressly for use with computers. Since I spend a majority of my day looking at computers it made a certain amount of sense. The glasses were not terribly expensive and they were polarized, tinted, and many reviews were positive so I went ahead and got a single pair to use. The company’s name is Gunnar, and they make a lot of "precision eyewear’ for gamers. I figured if it was good for gamers doing what they do, then it’d be fine for me.

I’ve been wearing my Gunnar glasses on and off since I bought them and they have served me well. There is a very slight magnification factor which I appreciate, I don’t need glasses right now, but I figure they may help combat eyestrain, and that they do nicely. The yellow tint may be helpful, the polarization definitely helps, but above everything else I have to say that my eyes don’t dry out so fast while I wear these glasses. Often times they’ll get a little too teary and I have to dry them, but it’s far better to have more tears than a deficit.

A few weeks ago, wearing my glasses I discovered that one of the very tiny nuts that hold the frame together had fallen off. I looked all over for a little brass-colored metal nut the size of a quarter of a grain of rice. So I contacted Gunnar customer service and asked them if they sold a repair kit for my glasses. The response I got back was amazing. Not only were they sorry my glasses failed, but they wanted to ship me free of charge a repair kit in the mail. I gave them my address and yesterday they arrived. It was an informal package, pretty much a sticky note with the pieces taped inside, then put in a mailer and sent via the postal service. When I opened up the mailer I could feel the little metal nuts poking through the sticky note paper. I opened everything up and there were 4 sets of plastic washers, metal washers, and the nuts. I sat at my desk with a pair of needlenose pliers and assembled the lost washers and nut on the one frame post that didn’t have any of that and tightened it down firmly like all the other posts.

It’s these little things that I appreciate. Other companies could just have rolled over and said “Buy another pair of glasses” but not this company. Because they are excellent glasses and the company has done right by me I want to recommend Gunnar brand as a good company to deal with and to buy from.

SupportPress In Action

Posted on June 8, 2012 by bluedepth

My first week with SupportPress has been magnificent. It was just in time as well, as we are looking down the barrel of a bunch of employee location movements which always requires lots of tickets and tracking because there are just so many discrete pieces to work with whenever someone moves from their established location to a new one, even if it’s temporary.

It’s also been a series of lessons when it comes to introducing new technology to regular folk. The adoption rate was much higher than I hoped for, as people were actually jockeying for “first ticket” so that felt really good. I’d estimate about fifteen percent of the staff have moved their communications channel to the help desk completely over to the new SupportPress system, while the rest have yet to break their old ways.

The old ways we still will respect. Having this new help desk system has given me moments of decision to make and learn from. Do I force people to only use the SupportPress system? Do I turn the office into a BOFH zone by forcing my clients to fold their entire communications structure into a ticket? Turns out I rejected that choice and elected to endure the steeper path of being, in what really turns out to be a human bridge, for my clients. So when someone drops by, someone calls, someone emails, or someone iChats us up, each time it calls for a ticket. SupportPress in this regard is really great, as we can create tickets on behalf of our clients and fill in all the details as if they penned the tickets themselves.

Another choice was one of statistics and performance. Now that the SupportPress system is providing us with ticket numbers and categories as well as ticket ages, the data is ripe for analysis, categorization, and the temptation to turn all of these raw numbers into performance metrics is very strong. This, as it turns out, is just another BOFH move that I simply cannot take. I refuse to use the raw data to measure any kind of performance metric – there is more to my life, to my assistants life than how many tickets we land or how old the tickets get before we tend to them. Here is a central tenet of mine, this system is meant to help only. It will never be used as a dashboard, it will never be turned into a yoke, or a bridle. The same way I rejected the before-mentioned BOFH move of forcing tickets out of clients, this is somewhat like the other side of the argument. The reasoning behind it is that I want people to use this resource. I want my employees (singular notwithstanding) to not fear that they will be lined up against some artificial measuring stick and slotted. I refuse to have First Trumpet, Second Trumpet, and Screwup Trumpet chairs in my orchestra.

There are other things that have occurred to me but I have rejected out of hand, brought about by SupportPress. I have considered and rejected a “Zero Ticket Friday” policy as fundamentally broken. What is so special about Friday that all tickets should be closed? If I institute that policy and some tickets are stuck in the waiting queue, do I penalize people for it? If you start making accommodations for things like “tickets can languish in the waiting queue forever” then what the hell is the point of the first move on this policy? Eventually it’s the self-defeating policies like these that create the bullshit of “It’s Friday, lets push all the tickets into the waiting queue.” It’s just dumb. So we aren’t doing it.

One thing that has come of SupportPress that we’ve noticed is that some of our clients have reacted less-than-happily about the sheer flow of SupportPress notification emails. The system sends an email when any ticket moves or changes, so clients could have at least two tickets (a start and an end) or up to double-digits especially if there are a lot of phase changes and clarification messages flowing back and forth. I personally don’t have a problem with notification floods as I am rather OCD about managing my email. I’ve written before on how I manage my Inbox – that any email has four potential destinations after they have been read. An incoming message can be stored in Evernote, sent to Toodledo, adapted and stored in SupportPress or outright deleted. Yes, I still use Toodledo, but I use it in conjunction with SupportPress. Some tasks, such as weekly reminders and such really fit better with Toodledo than SupportPress. Nobody really cares that much about getting constant notifications or trackability about daily, weekly, or even monthly tasks that I work on. Much of the regular things I do at work are “Andy does it, so we don’t have to worry about it anymore.” and so everything gets done and people can move on. That’s really helps illustrate the core features of SupportPress. SupportPress is designed to capture the discrete, non-repeating, highly interruptive traffic that any competent Help Desk must endure. There have been a lot of whitepapers written on the economy of interruptions surrounding Help Desk environments so going into it here would just be needlessly duplicative. The only really important thing to state about interruptions is that they are a necessary evil. People have to stop us to get help, it’s the nature of the beast.

SupportPress shines brightest when it comes to creating an abstraction layer between clients and the Help Desk. I like to think of the system providing a certain amount of slip between ticket arrival and first contact. In this way, SupportPress slays the interruption dragon that besets us. Instead of people electing to visit us or call us, which are the most interruptive, they can issue a ticket. We are notified that a ticket has arrived and that fact can be temporarily slipped in time so that we can conclude whatever function we are executing without having to endure the most dreaded thing of all, a context switch. Much like computers, interrupts and context switching is the number one gross consumer of time. These interrupts and context switches also threaten our quality of work. We can switch quickly but regaining traction once we’ve switched back to what we were thinking about before can be sometimes a maddeningly slippery proposition. I can’t count the number of times that interrupts and context switches have caused me lost time when dealing with a columnar data procedure such as checking items off of a long list. Where was I? Am I doing everything right? Why do I have this nagging doubt that I’m missing something? It’s this that I wish people would understand, and why when we ask people to issue their problems via ticket, why it’s so helpful to us.

So then we revisit an earlier point I had made, that I have elected to not force people to create tickets only. While this is true in spirit, I dearly wish people would on-their-own elect to use the less interruptive technologies available to them. The best thing for anyone to do would be to issue a SupportPress ticket outright, but if not that outright, then email or instant message also works well, because those technologies also include a modicum of temporal slipping that we really crave when we are knee-deep in some elaborate procedure. So while I refuse to force people to do a certain thing, I respectfully request that they do what they’ll do a certain way. Then it comes to how best to encourage people do change their course? First you have to let them know what it is that you’d like them to do, in a way, this blog entry may help with that as I suspect some of my coworkers read my blog and maybe they’ll notice the hint. One thing that can be done is rewarding people for using the ticket system by prioritizing those people who issued tickets with more force than we would otherwise pursue an incoming interrupt and context switch. It isn’t outright sabotage, but it does show that there is a preference and it’s in everyones best interest to respect us with the grace of a non-interrupt, and hence, non-context switching request. We’re driven to help and that is our passion and our purpose, but there is a best way to do it and for me at least, SupportPress is it.

So how much did it take for implementing this solution? We already have an iPage hosting account, wmichalumni.com, and frankly any host worth their salt would be just as good. I just like iPage because they are professional, no-nonsense, and cost-efficient. Any host can (and should) allow you to set up a free copy of WordPress.org. WordPress.org is an open source and free bit of software that creates a WordPress.com blog on a host that either you own or rent. The infrastructure of WordPress is actually perfect for what we are trying to do. The fact that it’s free is just a cherry on top. Installation of WordPress.org, at least on iPage is remarkably simple. It takes about 5 clicks and some little typing or usernames and passwords and preferences and the host creates a perfectly functioning WordPress.org instance for you. The theme, which is what SupportPress really is comes as a ZIP file for $100. Once you buy it, and then upload the zip file to your new WordPress.org site, everything else is pretty much a freefall into implementation. Falling down a flight of stairs is more complicated than installing SupportPress. Once the system is going, creating users is a snap, then introducing them is equally as easy, and before you know it, you’re up and running and your total outlay for the project was $100 for the theme and whatever you are paying your host.

So, then that begs the question of why we don’t self-host. I chose to not self-host because there is a field of tar which would ruin usability. iPage has unlimited bandwidth, unlimited storage, and since we are already paying for it to do other things, it’s arguably ‘free’ to do our SupportPress infrastructure. I don’t have to endure needless bureaucracy and it’s available anywhere and anytime without me having to muck about with VPN technology or anything else. It’s not that what I am avoiding is that onerous, but this way is far far simpler and is much more satisfying to me in that the path that I took got it done. From zero to implementation with nobody to argue with, nobody to ask, nobody to cajole, and nobody peeking over my shoulder.

I think that any Help Desk, especially one in academia, but really this extends to any other industry as well could really benefit from SupportPress. I like to reward products that please me and do their jobs well. When I find a product, like SupportPress, I flog it for all it’s worth. My only regret with SupportPress is that I didn’t have this technology 10 years ago. I am blessed to have it now and I plan on continuing to use it and I plan on taking it with me wherever I roam in the future. If anyone has any questions about anything I’ve written here, you know where to get ahold of me. I welcome questions on this, SupportPress is that good.

SupportPress

Posted on June 2, 2012 by bluedepth

I just rolled SupportPress out to the rank and file at work. Or at least I thought I did. My day was going so well, so smoothly. I got my introduction email with graphics sent out (or so I thought) and I got all the invites shipped out as well. Everything was going just peachy – until I looked at the sent mail and noticed that when I sent the message by copying all the discrete addresses that only the first address took. So I didn’t send out any message at all!

To really get a grasp on how irritating this was, I couldn’t send a message to the LDAP alias that expands out to all the people I work with, the address is dar-staff@wmich.edu. The SMTP server at WMU was rejecting it out of hand. Turns out I figured out why – it was the screenshot graphics. That system they have rejects mail with pictures. So I had no choice but to copy down all the addresses from our Wiki and do it manually. Turns out when you copy that kind of information into Sparrow, it only looks at the first address and ignores everything else. It was my thinking that it would see the commas and figure out I was copying in 48 addresses. No, just one really long address.

When I noticed this, all I had was my iPhone and I was having lunch with Scott. I was cursing Webmail Plus and the LDAP directory for placing artificial limits on email and so I figured I could get the list of addresses and paste them into my iPhone and use the Mail app in my iPhone to do the heavy lifting. Turns out it suffered the same mental block, treating the addresses I pasted in as one giant address. So after lunch was over I was in my car trying to tap and copy one address at a time in. This is another bad idea because if you tap and don’t hold the iPhone thinks you want to email to just that one person and so dumps the draft you were working on and starts a new draft with an empty email. The forwarded bit with all the text and graphics? Lost. Three times lost. I was successful in the end, shipping my intro email out to all my coworkers despite all the technology surrounding me meant to make things easier.

Alls well that ends well, so we’re up online with SupportPress and I have to say that I am very happily surprised with what I see. Clients see a very simple version of the site and it’s compatible with every browser, every computer, including iPhone and iPad to boot! Now that I’ve let the genie out of the bottle it will be very interesting to see how it is received. There has been lots to say on that topic before, and in another post, a more private one, I’ll go further into the nitty gritty details.

So despite technological hurdles, I was able to get my automated help desk system off the ground and show it off to people. Monday is going to be a rip-roaring day, indeed!

TL;DR

Posted on May 18, 2012 by bluedepth

Information on the network is perpetually increasing in volume and so I find it progressively important to seek out tools that help me parse, limit, and control the flow of the information that is out there raging by like an enormous wordy river. I started my personal evolution in many places other geeks do – old skool with newsgroups. Since then, Usenet has been abandoned and shuttered and handed it’s info-river crown off to RSS and ATOM, which are ways of syndicating content from websites and aggregating that content in one framework. In a lot of ways, these systems are effectively joining the little rivers into a giant monster river that goes gushing by.

This is the first step. Anyone who attempts to put their head in this river only sees a blur as it rushes on by you, maybe you’ll get a hundred stories but the majority of it will pour on by without one iota of attention from you. This didn’t last too long and then the next step came, which was social curation. People follow other people and the ones who are the most popular are the ones curating the epic flow of information and bringing only the things you are really interested in to your attention. These social networks are like fishermen on the raging river of information, they catch bits and pitch them over their shoulders and they slide down the duct towards their followers. You don’t have to worry about the raging torrent anymore because you have faith that anything worth your attention is ending up in that duct running towards you.

Something really foolish happens next, you start to aggregate the ducts together and now you’ve got a smaller version of the giant raging torrential river except now it’s sorted, somewhat, but still rather too swift to catch much.

Then comes instapaper and all the other “read it later” services. When I see something that I sense may be interesting, usually by headline or keyword I will tap on it’s link and send it to instapaper for keeping. It’s as if the matchsticks in the raging torrent are getting picked out, then aggregated and the smaller torrent is being picked over by me and then serialized. The information waits, and I move through it item by item at the pace I am comfortable with. Now, the rate of information loss is immense. It’s meaningless to return to the giant torrent, the curators are just as noisy as the torrent is itself, the ducts might as well be the new torrent, and the tools you use are making uncomfortable squealing sounds under the pressure of how much we are effectively serializing.

Then as I read through my instapaper queue I finally reach the last point on the journey of raw information reaching me in the 21st century. Either I like it and archive it or save it in my evernote “for ever” or, and this is actually turning out to be a new theme, I brand the information TL;DR. It stands for “Too Long; Didn’t Read” and I find myself reading just a few sentences of what at first looked compelling and then realizing that either I don’t care or I don’t agree and then out comes the TL;DR stamp and the information is pitched into the big bit bucket in the sky.

There is something new coming, and I’ve seen an inkling of it with an iPad app named Thirst. It acts as a kind of content aggregator/curator for twitter traffic, another raging torrent of information and categorizes tweets and brings other content along for the ride. I think it’s really quite something however I can’t really make good use of it because my iPad is just too old for such an app, it jettisons after a few moments of use. Alas, there will come a day when we set up networks of aggregators and curators in spiral arrangements so that the final product is an intensely hyperlinked virtual meta-document delivered on some sort of display technology.

Something like this I find will really only work and make most people happy if we borrow a theme from email and arrange it serially like with instapaper. New material is always flowing into the queue but we can scan the queue, comfortable with knowing that nothing will go unseen, and able to give our attention to the stream of incoming relevant, curated, categorized, and hyperlinked information. Like a DVR helps people by timeshifting television information, whatever this new second or third generation information application will also perform the same duty.

Speaking of television, a great majority of it is TL;DW, or TB;DW. Too long or too boring. Perhaps we’ll extend it to TI;DW. Too inane; didn’t watch.

This blog post is already TL;DR, but at least I know it and celebrate it.

International Day of Lying

Posted on May 15, 2012 by bluedepth

People need lies. Lies are good.

At least when it comes to your online identity. I’ve been reading a few things here and there with people who are quite upset that Mark Zuckerberg is seeking ways to dodge his fair share of paying taxes and these people are very upset that Facebook is making money off their personal details – their lost privacy.

So how does one regain lost privacy? Simple, lie. Lie right through your teeth. Make lying an art form. Create a fantasy life out of pure whole cloth and make it as bombastic and marvelous as you have creative chops to make it!

In fact I think everyone should do this. Right now. We need a international day of lying. Everyone needs to log in to Facebook, Google Plus, and Twitter and go to town. Change the years, fiddle with the places, come up with schools you didn’t attend and live in cities you have no idea about beyond their brief entries in Wikipedia. Make it all random, make it monumental, but above all else, make it a lie. A big beautiful fantastic fabrication!

To that end, I’m going to edit my Facebook to this end. It’s going to feel good. Oh so good. Why don’t you join me? Nothing says pleasure more than wrestling power away from those that do not respect you, like Facebook. And Google. And Twitter. And well, anywhere else really.

Monetize that bullshit. I DARE you!

Of Clouds and Stones

Posted on May 14, 2012 by bluedepth

The early 21st Century will be known for the era of cloud computing. Just a little bit of what the cloud can do I’m actually taking advantage of right now as I write this blog post.

Google provided a huge space for people to upload their music and created a handy tool to upload their iTunes music up to Google’s storage system on the network. I took advantage of this offer and copied my entire iTunes library up to Google. That’s of course just half of what I needed to cloudify my entire music collection. I also need a client to play the content on whatever devices I want to use them on. Unfortunately the Google webapp for their Google Music service doesn’t work well on my iOS device, however there is an app called Melodies which does work fantastically well!

This has saved me so much time, expense and bother. Instead of having to buy a device with a big storage unit for my music I can simply stream my music off the network, using Google and Verizon (and Wifi if I have it, and that is almost universally ubiquitous in North America anyways) so now I have nearly universal access to my music, in a way having my cake and eat it too.

This wasn’t always easy, the Melodies app did have an issue with not being able to shuffle properly but after I contacted the app support staff and telling them what was wrong they fixed the app and it updated on my iPhone in a few moments. From that point I have realized something I never thought I’d be able to do, but play my music right off the network. It’s just one more way that devices, storage, computers, all of it are becoming increasingly abstracted away from my computing experience. I expect that sometime soon the notion of a computer will start to erode and evaporate as more and more of my life becomes cloudified, or perhaps the right word is enclouded? Going to have to work on the terminology.

Of course, people who I’ve spoken to about the cloud come up with very familiar complaints as to why they don’t want to join me. Mostly it comes down to a question of privacy, and that they feel the cloud would endanger their sense of privacy. I’ve thought about that point for a while, trying to come up with a position on it. I’ve honestly never really given two shakes about my precious privacy. What value am I coveting? So what if Meijers knows what I buy and when I buy it? So what if Google knows what music I enjoy? So what if I’ve been categorized and indexed? Where is the hazard? People regard privacy as some sort of grail-object. They protect it beyond all rational sense and I don’t think that any of us can maintain any sense of privacy any longer, at least since social networking became a mainstream part of our lives.

But then again, there is the fear. Where does that come from? People hiding who they are, what they think, what they buy from others because we’re afraid of, what exactly? Isn’t it a more comfortable life to simply be who and what you are and let the chips land where they will? A life exposed is a non-issue for those that are proud of who and what they are. I admit to having a definite cavalier attitude when it comes to my privacy, but what the hell do I have to hide? Or any of us? To me it has always been my argument that if I reveal elements of my life to strangers that somehow they’ll take advantage of that information and somehow misuse it or attempt to hurt me. Well, first and foremost they’ll have to endure the social awkwardness of being the ones to expose my “secrets” to everyone else. The key here is to own everything about yourself. Own your passions, own your foibles, and own your mistakes. Nothing about the past means anything, regret is a dull nothing. For example, Anthony Wiener’s crotch-shot being publicized lead to the end of his political career. WHY? I respect people more when they stand up and own whatever it is that others find outrageous. Here’s the thing, none of us are pure. None of us really have any place to stand and throw stones. Even Jesus Christ spoke on this very point. “Let him who hath no sins cast the first stone!” Well? So you have a picture of your tenty underwear out there? OWN IT. BE PROUD OF IT. In fact, go on a Playgirl shoot and show the world your junk. This idle and meaningless outrage is stupid and lame. I would pay real money to anyone who could prove beyond a shadow of a doubt that any random other human being isn’t a sexual pervert loaded with monumental loads of kink. All it takes is a shot of whiskey to get a man to drop his shorts and do highly entertaining things with his body.

So what it comes down to? Privacy bent to protect the image that we’d like to impress upon other people that we are all pure as driven snow? How silly is this, when we are as pure as driven-over snow! At least have the fortitude to stand up and say “Yes, that’s my junk shot! Do you like it!?!” Because in that, lies respect and honesty.

To people that feel differently than I do, I have a one word question to ask you:

“Really?”

Bluedepth's Journal

Thoughts & Opinions

Category Archives: Web Finds

Superpass Password Hasher

Dell Exec: The iPad Is Too ‘Shiny’ For Business | Cult of Mac

Gunnar Glasses