Fake installer malware makes its way to Mac | TUAW – The Unofficial Apple Weblog

Fake installer malware makes its way to Mac | TUAW – The Unofficial Apple Weblog.

When it comes to installing things on your Macs I often times advocate a rather carefree attitude. One thing that has always been true, and this article just nails home the point, is that even the most secure system can fall if the person holding the keys is tricked or cheated into opening the door.

I have said to many people whom I’ve given computer advice, if you have doubts, please contact me and I can look at it and give you advice. It’s free, and I’d rather help in the vein of “An ounce of prevention is worth a pound of cure.”

Facebook Notification Autodisplay Trick

I recently moved over all my old Facebook Notes entries from the past and copied them into my Day One app for posterity. In the wayback machine I found an entry from March 25th, 2009 regarding a neat little thing I found that makes Facebook a little more neat. The entry back then covered how I found a way to make my Firefox browser automatically open up Facebook notifications as new tabs in my browser window all on it’s own. So as people that are connected to me on Facebook do things that fire off notifications, those automatically create new tabs in my browser and I don’t have to worry about playing catch up with the notification system and then overloading my browser with 20+ notifications. As I do other things my browser can tend to Facebook all on it’s own and I can look over the notifications in a more organic and pleasing way. I’ve just found a way to do the same thing on my Chrome browser and for anyone who is interested, here’s how I did it:

1) Start Chrome
2) Find the Chrome Extension RSS Live Links and install it
3) Browse to Facebook and click on your notifications, then find the RSS link and copy that to the clipboard.
4) In the options for RSS Live Links, add the RSS entry to the extensions RSS list and make sure you set the refresh time properly to where you want it and then check “Automatically open new items” checkbox. Click Save.
5) Save the extension options and then you are all set.

The extension will scan the RSS feed from Facebook every five minutes and if it notices changes it will automatically open up those new items as tabs in your Chrome browser. When you are all done, you can minimize your browser and do other things and over the day your browser will automatically fill with all the little notifications that Facebook throws down all on it’s lonesome. Then you go into your browser, see the notifications and then close the tabs (Command-W) when you are done with them. Easy peasy.

Workflow with Pocket

I have recently fallen into a peculiar workflow arrangement between various social networking applications and Read It Later’s Pocket application. When I am following the flow of status updates from my Twitter stream I prefer to stay in-the-moment with the stream and select interesting-looking tweets that have links attached to them, but instead of actually following them in a browser, I send them to Pocket. My preferred Twitter application, TweetBot makes this as easy as tap and select “Send to Pocket” with a happy little sound confirming that my action worked. This really works well for me and doing this has spread beyond the confines of Twitter out to Facebook – however there is no convenient interface between Facebook status posts and Pocket so the workflow is a little more convoluted. I command-click on perhaps-interesting Facebook posts and this opens them up in tabs. Then I switch to the tab, click the Pocket extension, send the link to Pocket and close the tab. I don’t really want to see the links right now, I’d rather send them all off to Pocket and then queue them up that way.

Another really neat web tool that I’ve fallen in love with is IFTTT.com. This site allows you to connect a huge collection of services to their site and then construct “If This Then That” rules. This has actually simplified the Twitter-to-Pocket interface, in so far that if I like a Tweet then that is plucked by IFTTT and sent off to my Pocket automatically. This particular bit does muddy the waters between TweetBot and Twitter itself, but it’s not really a problem, just a build-up of near-miss convenience. IFTTT in this arrangement shines when it comes to Google Reader. I have subscribed to quite a lot of RSS and ATOM feeds from various sites and manage them all in Google Reader. If I “star” something in Google Reader, then IFTTT notices and copies that entry to my Pocket for later reading. As I am quite fond of having my cake and eating it too I’m always on the lookout for multi-product synergy and convenience. I really do not like Google Reader’s web interface, in fact, I really don’t like many “Web Interfaces” for products and would prefer the gilded cage of specialized client software instead. So there is a nice synergy between Reeder on my Mac computers which presents my Google Reader contents in a visually appealing way as well as Flipboard, which is the preferred way to view Google Reader on my iPad. By using IFTTT as the middleman-behind-the-scenes I can funnel all the stories that catch my interest and collect them right into Pocket.

All of these things can also be done with Instapaper and I was an ardent fan of Instapaper for a very long while, but I’ve switched over to Pocket. I still regard Marco Arment and his product to be very good, but for me personally I found that Instapaper on my 1st Generation iPad would jettison too much for my liking. It wasn’t as much a problem with Instapaper as it was the iPad itself. Embarrassingly outclassed by the applications that I was trying to force on it. I’d be able to stand by this, but Instapaper on my 3rd Generation iPad also jettisoned. I didn’t really want to bother the author with the yackety-schmackety bug reports and Pocket edged out Instapaper when it came to displaying video and audio media. The core functions between the two are quite similar and the only other small feature that pushed me over to Pocket was the ability to search on my Pocket list and perform actions on multiple items. I have no doubt that Instapaper will catch up and may already have caught up. The money I spent on Instapaper was money well-spent and I would suggest that people look at both apps before deciding for themselves.

So back to the workflow, this is how I naturally started navigating my social network stream of information. In a way, I follow sources which curate the noise of Reddit and other news aggregators into categories that I find most interesting and then I self-curate the longer pieces into Pocket for later consumption. As I used this workflow it occurred to me that what was happening was an emergent stratification of curation. Living generates a noisy foam of information, which crashes on the coral reefs of StumbleUpon, Reddit, Engadget, HuffPo and the like. Information seagulls, like @geekami (for example) fly over these coral reefs of information and pluck out the shiniest bits, linking them to tweets and shipping them out. Then I come along and refine that for things I really find interesting and all of this ends up crashing into Pocket. Arguably, Pocket is the terminal for all this curation, but it doesn’t have to be. I could (but I don’t) cross-link Pocket and Buffer using IFTTT and regenerating a curated flow of information turning me into an information seagull. I suppose I don’t follow that path because I already have enough to do as it is, reading, comics, FOMO, work, gym… the list goes on and on.

For all the apps and people I mentioned in this blog entry, I really do recommend that you Google them and see if any of this fits in your life as it did mine. If It works for you, or you found a better way of managing this flow of information foam, please comment with your workflow description. Just more curation. Lexicographers and Encyclopedists eat your heart out. 😉

Citizens from 15 states have filed petitions to secede from the United States – Dallas Top News | Examiner.com

Citizens from 15 states have filed petitions to secede from the United States – Dallas Top News | Examiner.com.

The list includes Louisiana, Texas, Montana, North Dakota, Indiana, Mississippi, Kentucky, North Carolina, Alabama, Florida, Georgia, New Jersey, Colorado, Oregon, and New York. Of that list, I would be dismayed only for the last three, the others? I couldn’t push them out the door fast enough.

What’s most curious is that most of these states consume a lot of federal money. If they left the union, life would become very difficult for them. Just imagine the new tollways that would open up on their now-not-federally-supported-segments of the Eisenhower Interstate System. You thought the NYS Thruway was an expensive axle-mangler, just wait until Albany has to figure out how to fix it all on their own.

I think we can all say with a fair amount of humor, that Texas can leave whenever it damn well likes. Stop posturing and threatening, just do it already. I can’t wait to see how OPEC deals with The Great Christian Domain of Texas. That’ll be hilarious.

Hurricanes that slam into Galveston will now be regarded as Reality TV as “Those poor fools in Texas” try to cope without the rest of us. A lot of these red states think they can exist outside of all socialized connections with the other states and the Union, and I think they should be allowed to leave to feel what being truly alone feels like.

How fast they would rush back. And my, what sort of concessions they’d have to part with just to get back in. Just ask South Carolina about secession. It’s been more than a hundred years and they still haven’t recovered from the last time. But you never know, it might be different this time. (no, it won’t, it’ll be worse)

How Lovely

I just got an email from my blog about a comment that was posted about my earlier post regarding controlling ammunition. There is no hidden agenda on my blog, I am a liberal and I proudly defend my opinions and thoughts and when it comes to weapons, what I write comes from the heart.

So, on with the comment from a user by the name of Joe Joe, email address bgyiu@gmail.com from IP address 166.152.62.75:

Move to chicago or new york ass munch. They have almost completely dis-armed their citizens, and now they are at the mercy of thugs who don’t follow the law anyway, dick mouth!! It’s candy ass turds like you who are the first to be raped and killed. Just because you don’t mind being defenseless, don’t expect the rest of us to be so anxious. Cowardly turds like you are precisely why this country has become a joke. Even if the criminals didn’t have guns, then we are at the mercy of an out of control, authoritative government. NO THANKS!!! Just move somewhere where they have disarmed everyone and allow YOUR family to be raped, pillaged, and plundered!!!! Keep your warped agenda to yourself, butt munch.

So that comment of course is certainly provocative. I find the actual word selection to be most interesting to me. Let’s set some assumptive defaults regarding the poster of the comment – first, I think it’s safe to say that anyone who reacts this way is likely a conservative and if so, we have to have pity for them because they are political lepers. Nobody wants to engage with them because all they have is vitriol, anger, and reactivity. This particular fellow also has a uniquely bent vocabulary.

Let’s move beyond the fear of control from the government and get at the core pillars of the comments contents. The first one is fear. This comment reeks of fear. Fear of criminals, fear of the government, and fear of what I said in my blog. I don’t feel anxious or attacked by the commenter, I feel sad for him – as I would anyone who lives in that much fear eventually would de-evolve into nothing more than a gross sort of pavlovian kicks and jerks. Now on to what really is entertaining about this comment, and these words are at the core of it: “ass munch”, “dick mouth”, “candy ass”, and of course, “rape”. Now my higher education is in psychology and english and I can’t help but feel excited at these very colorful phrases. The writer reveals more to me in his word selection than the actual content of what he is trying to convey. As I have said time and time again when it comes to conservatives who are so angry and upset with homosexuals, it has more to do with them fighting their reflections than it does anything else. This fellows comment is a perfect example of this. A rational argument could have been made without all these colorful epithets however this fellow spent time typing these in. I think this commenter has a deep psychosexual issue that he has not dealt with yet. He is typing “ass munch” and he is thinking about analingus. He writes “dick mouth” so obviously fellatio is foremost on his mind, “candy ass” has a rather well-known connotation to cowardice however when this phrase is in the same statement with the others, it’s not cowardice but rather a begging for anal sex. In the end we get to “rape”, and that imagery comes up quite a lot. I am unsure as to whether the commenter is fearful of being raped, anxious about having rape ideations or what, but he spends a rather long time thinking about it. I’d have to say that the phrasing is homosexually receptive, as it’s something that bottoms are fond of in general. So the commenter is probably a closet homosexual with ideations of being overwhelmed by a more masculine partner and likely fantasizes about having his will dominated by another man. The popular image of this is the ultra-butch muscle mary who at the drop of a hat drops their shorts for a righteous pounding. I would say that in the extremis, this fellow, if he wasn’t ruled by fear, would probably enjoy anal sex and from the sheer massive content of homosexual phrasing in such a short comment,  how could anyone see it any other way?

So, I feel more pity for him than anything else. Joe Joe, I hope you stop trying to troll blogs like these because your deeper psychology is leaking out in your vocabulary and I suspect that you really would prefer people to not know of how much homosexual ideation goes on between your ears.

As for the message you tried to convey? It is lost on me. I know what you wanted to say and stripping off your homosexual panic and the fear, I do get you, however I still do not agree with you. I still believe that controlling ammunition is the best way to control guns. Obviously it isn’t a topic that a liberal or a conservative is willing to budge on so perhaps leaving the comment was a faux-pas on your behalf. In any case, you did entertain me and for that, I am thankful.

You should  do something about all that homosexual panic though, it’s not good for you. Really.

Dust a Meeting

Meetings are insatiable productivity black holes that complicate lives and ruin workplace flow. I recently tried a collaborative online system called Basecamp in order to asynchronously develop a software strategy at work. What I wanted and what I observed diverged so thoroughly that there was absolutely no point in continuing with Basecamp as it was just in the way. The entire endeavor made me a little sad, not a huge fan of failure.

Meetings themselves are time vampires. I loathe them with every fiber of my being. They are massively interruptive and obnoxiously presumptive. You set aside a date and time and a place where people have to attend to discuss some topic. A meeting is a monster even when it’s in the cradle, being thought up by someone who desires to meet. Out of their heads pop a snarling tentacled beast with sharp fangs that serves no purpose but to interrupt flow and get in everyone’s way. Even the birth of a meeting is an arduous agony, with each participant (or combatant) the multiplexed temporal complexity grows. Two people can find a time to meet. Three people and it’s an order of magnitude harder. I was attempting to arrange a five-person collaboration and I wanted to avoid a five-person meeting with every ounce of willpower I could muster. My intentions were to establish a five-person collaboration which leveraged technology (Basecamp) to achieve speed and productivity because all five collaborators could function asynchronously. You could contribute what you felt you had to when it was right for you. It respected flow and was not supposed to be interruptive or presumptuous. Alas, the road to hell is paved with good intentions and this particular road lead to the very specific hell of a worthless unwanted but agonizingly unavoidable and loathsome meeting.

So now my efforts to avoid a meeting inexorably landed me right into setting a meeting up. Of course it was obvious that right after the first few responses I could tell the tell-tale sloppy-wet-sucking-sounds of a baby meeting unfurling it’s tentacles in my midst. The first agony of course is finding a time when everyone is free for a meeting. So right off the bat, two weeks went down the toilet as we had to wait for everyone to be ready. Then assembling it was a pain. It used to be easier with Groupwise, as a meeting organizer could see the public calendars of all the participants and select the time that would be best and then send it to all the participants which really reduced the interruption of flow quite a lot. Alas, we led Groupwise out behind the barn and we did-what-must-be-done. After we were done burying the corpse of Groupwise we were back to the way it was before – so A emails B, C, D, and E. Then they all reply, and then A shakes the magic eight ball and everyone agrees that in three weeks, we’ll all have time. It’s a lot of back and forth and this and that and it creates a nasty haze of meaningless email exchanges. So, the meeting is ripe for tomorrow at 3pm. Great.

So now I wait. I have a list of all the software we currently use and instead of spending the past two weeks discussing, asynchronously, the merits and flaws and coming up with a solution in at most a weeks time, this nascent baby meeting will likely take another month before there will be any resolution. Tomorrow is just going to be the First Meeting, where we trot out the new baby time vampire and give it a good feeding.

It’s a terrible way to do work. It trashes flow, it lowers morale, and it sucks time down a toilet drain. At least people aren’t fond of the parliamentary species of time vampire meetings, where you spend the first few iterations of the meeting discussing protocol on how subsequent meetings are to be held. That form of meeting is older, and much worse. I really must count my lucky stars that we usually only have the easier-to-cope-with modern meetings where the first three get-togethers aren’t set aflame with discussions on what words mean, how we are going to proceed, or what the definition of is, is.

There is wreckage however, even with a modern meeting. The person who had a problem and started all of this still doesn’t have what they need to get work done – we’ve been waiting for that special moment to arrive when we all can pet the baby time vampire and let it ruin our working lives. I can’t really get worked up very much, as least not as loudly as I used to a long time ago when I felt I could change things. It was pretty much obvious from the start that when the discussion immediately derailed with that most hated of questions “So, when shall we meet?”, heh, that was it. I knew that asynchronous collaboration was not going to work.

What’s really quite sad is that the technology has developed quite well and very elegantly. You see the edits and the collaboration realtime, there is “What’s new” and “Catch up” features, it’s free for 45 days, all of it – right there. Ready, willing, able, and if used, the promise of reaching a solution sooner-rather-than-later can be realized. Instead of that path however, we are going to have a meeting.

Not that anyones life is on the line for the work that has to be done, just the soul-crushing dread of having to endure another time vampire meeting. Having to go somewhere at a specific time, putting everything else on hold while we all waste our time and energy. The wry humor in the idea that we could have been already in the yea/nay phase and quite possibly be sending orders out to finalize the entire project, it could have been that way.

What have I learned? That I won’t ever do this again. Part of the agony of watching a grand design fail is watching it fail in flames. Modern business culture just isn’t ready for the kind of asynchronous ease and productivity that these tools can provide. I’ve written before, tongue-in-cheek that hateful meetings are like intellectual memetic herpes. It’s a theme that we play over and over again, not because actually having meetings leads anywhere but that instead we’ve always had meetings and our peers seem happy and life goes on, so why seek out anything else? It’s an idea, a meme, that is replayed again and again. The fact that meetings are time vampires that suck all the happiness and color out of life isn’t actually a part of the deal. Nobody seems to notice. Every once in a while one of us wakes up and shakes their head and asks “Why the hell are we having these stupid meetings?” and then tries something novel. Then that detestable question, “So, when are we meeting?”

That question should be engraved on a gun. Instead of asking it, just load one bullet, spin the revolver chamber, clack it home and pull the trigger. So, in the end this is all so much bellyaching over nothing. Asynchronous collaboration isn’t ready yet, or more specifically we aren’t ready for it, yet.

Not every industry has this problem however. You see companies like Automattic, which is the parent company that manages the WordPress technology – they make use of the P2 theme which is a central driver (so they say) in how they manage their projects and such. I’m sure Automattic has meetings, but I suspect that they use asynchronous collaboration a lot more elegantly than is done in higher education or the non-profit sector. When I first started exploring Basecamp, for example, I was blown away. I could collaborate with my assistant and material would build because when we were both working on the project and working together as a team brought a kind of science-fiction cool to the dull things we were collaborating on. There is something quite breathtaking about watching an entire project morph and change and grow as you sit there and watch it. Like timelapse only in real-time. Another little bit that I really found super-compelling was how these technologies enabled asynchronous collaboration and respected workplace flow. There was no interruption, if you were in the middle of a task you could polish it off quickly and confidently because time wasn’t important. The collaboration could occur at any time. It also occurred to me that asynchronous collaboration might also benefit from the differeing themes of cognition during different parts of the day. That you are more clever for some things right after dinner than you are before tea, or if you wake up at 11:30pm with a sudden Eureka moment, you could hop on to Basecamp and share your stroke of genius.

Alas, this is all just prattle against the memetic herpes epidemic that is the meeting.

It warms my heart to imagine a world without telephones and no rooms in which to meet. It would preclude meetings completely and banish them to extinction and force asynchronous collaboration. *sigh* It’s only a dream I suppose.

When mice are put into enclosures with limitless resources, their social behaviour degenerates dramatically. – Science – Aug 11, 2012 – Interesting Facts and Fun Facts – OMG Facts

When mice are put into enclosures with limitless resources, their social behaviour degenerates dramatically. – Science – Aug 11, 2012 – Interesting Facts and Fun Facts – OMG Facts.

I love these studies! They prove beyond a shadow of a doubt that without space travel Humanity is pretty much doomed. I can’t help but think of Star Trek. In that fictional universe there is no want, no need, Earth is a literal paradise. I wonder what would happen to that Universe if you kept everything else the same but eliminated warp travel from the story.

You’d have Universe 25. It wouldn’t be pretty. HA HA HA.

So what is the most important thing in the Star Trek Universe? Warp Travel. Beyond everything else. LULZ.

Hawthorne

While running my SupportPress system for several months now it dawned on me that the  MySQL database that lurks just behind the scenes is collecting quite a bit of accidental detail on my coworkers that use the system. Nothing that would endanger anyones privacy, so quickly put that notion out of your head. What it does do is record the datestamp of when people enter tickets into the system. Generally people enter tickets right after they’ve identified a problem, of if they come to us, we start the ticket as the first thing we do, so again, the initiation of a ticket is in a general sense linked to just after the problem was detected and brought to our attention. For the remainder of this post, I assert that the datestamp on the ticket is when the problem occurred.

So with a middling amount of database skills and analysis under my belt I decided to run some aggregate queries on the data. Here’s what I found:

When I aggregate all the days of the month together and count how many tickets were initiated on which particular days I discover four notable days where things seem to on-average, go haywire: The 1st with 81 tickets, the 6th with 66 tickets, the 12th with 56 tickets, and the 23rd with 79 tickets. What’s really interesting about this dataset are the dates on the opposite side. The least haywire day is the 31st, with 11 tickets then the 28th with 20 tickets and the 3rd with 28 tickets. So now I can say, in general, that the 1st, the 6th, the 12th, and the 23rd are “Days That Suck”. The best day is the 31st.

I ran the same analysis but instead of days of the month, I used hours. In general the mornings are where people seem to have the most problems. 14 tickets at 7am, 201 tickets at 8am. At Noon the tickets drop by a hundred, then from 2pm to 4pm it rises gently but nowhere near the morning values and the afternoon peak comes between 4 and 5pm. After 6? The rush of tickets just stop. People don’t report problems when food is on the line. 🙂

The last analysis I did crossed day and hours together and counted the tickets. This had some interesting data in it, since I was just looking for any notable outliers. Hours and Days where the ticket level was say, more than 20 for that hour. Here’s some of the “Problem Days and Hours”: The 1st of the month at 10am and the 23rd at 10am.

What is to be determined from these really general findings? There are some cursed days at the office apparently. The 1st, the 6th, the 12th and the 23rd are really quite troublesome for people. Mornings are rough but on the 1st and 23rd, at around 10am the shit hits the fan.

SupportPress collects this data for as long as it runs and I’ve no intention of stopping so the further we go the more (or maybe less) pronounced these interesting bits of information will get. Those that work with me that also read my blog might have some insight or they may just find some of this helpful if they have spare vacation days to spend and are looking for some reason to not come into work.

SupportPress At Work

Several months ago I became aware of certain workplace changes that were going to only be a problem if I chose to ignore them instead of doing something about them. There’s always been a part of my job that I’ve been kind of awkwardly ignoring. I lacked any kind of real instrumentation to one of the major aspects of my job, in fact, it’s the part of my job that I regard as being truly central and my “first hat” and that would be the Advancement Services Help Desk. First and foremost I go to work to help people use technology. That I didn’t have any online structure in which this fit has always bothered me. I always rationalized it as “My shop is too small to need such things.” or “It’s too expensive and I can’t prove that the ROI will justify the price.” but all that changed when given a purpose by a workplace change that was coming, and me discovering SupportPress.

SupportPress itself is a WordPress theme for a WordPress.org installation. We already had a hosting company that we had a great relationship with, [iPage](http://www.ipage.com]. It struck me that while we had a site with the host I certainly wasn’t making the most use out of our investment as I could. After a long while I logged into iPage and noticed their SimpleScripts service off their Control Panel. SimpleScripts is an interface to install very popular LAMP-based scripts that add features to a hosted website. Various scripts include WordPress.org, Drupal, and a gaggle of other ones including some eCommerce scripts that I really couldn’t care more about. WordPress.org is the free-to-use DIY version of WordPress.com. WordPress is a wonderful blogging platform and it serves as the bedrock that SupportPress runs on. So setting up the WordPress.org site was exceptionally easy. It was a click and some typing, followed by a few more clicks in SimpleScripts and it was done just like that. A fully featured and functioning blog running on my web host. After that, I looked at SupportPress and discovered that the theme sold for $100. One payment and you get a license to run it on as many blogs as you like. It wasn’t a subscription, just a straight simple sale. After buying the theme from WooThemes I downloaded it in it’s native form, one single ZIP file. I opened up and logged into my WordPress.org blog and navigated to the administration side of the system and right there, as easy as you please is “Install Themes Here” and the preferred option is “Install Theme from ZIP”, which I had exactly! So I uploaded the SupportPress Theme ZIP file to my newly made WordPress.org blog and when I applied the theme and went out to my blog, everything was functioning as promised! Everything! A fully functioning Help Desk Support System was running without any extra tomfoolery. I didn’t need to muck about with source files, fiddle with settings or update anything to get things to work as they should. This software, all of it, from end to end is what writing ELEGANT system code looks like. It works without guff, simply, directly, and elegantly. After that, all I had to do was create user accounts for all my clients, assign a few as “Administrators” like my assistant at work and I was done. I had the entire project from plan to finish in about an hour!

SupportPress has two distinct interfaces. The first interface, the one I use is the “Administration” interface. It very closely resembles the “User” interface but has a lot more options. If I need to perform anything more in-depth I can always call up the WordPress.org administration interface itself (which supersedes the themes administration console, wrapping around it actually) and I’ll show off both interfaces in this blog post. The system is organized on the management of Tickets. A ticket is a self-contained event that requires help from me to my clients. A ticket could be anything from a lost password to a report that a copier is malfunctioning. A ticket in SupportPress has a title, a description, a status, a type, an owner and an assignment. As an administrator I can see every single ticket and manipulate every single ticket. I can change ownership (the client), the assignment (who is to help), the status (which all new tickets start as new), the type which indicates what category the ticket belongs in and I can add comments and attach files, anything that can be done in email, except it’s logged in a database. The best way to describe it is to show it:

SupportPress Administration Screen

SupportPress New Tickets

SupportPress New Ticket

This administration interface is a full-view while the next few screenshots show what the client sees. It is much more direct:

SupportPress User View

The system is a pleasure to use and goes so far as to suggest top-ranked KB articles for clients as well as displaying all the clients tickets and their statuses with two buttons that are clearly marked for starting new tickets. When clients type in a title for a new ticket the system will automatically (while they type!) scan for relevant KB articles and display them. Eventually as the KB becomes more robust users will start to discover fixes in the KB on their own and in some situations actually be able to help themselves. When a user submits a ticket, the administrators get an email notification and the ticket resides in the system as “New” and assigned to “Anybody”. Any of the administrators can log in to the SupportPress system and look at these tickets and assign them either to themselves or other administrators.

When an administrator makes a change to a ticket, that change is sent as an email notice to the client. Everything you do to a ticket ends up being sent in an email every time you submit a change. So if I see a ticket, assign it to myself, set it’s status to “Open” and change it’s type to “question”, for example, the user will get an email showing what category was changed, the old value, and a graphical arrow pointing to the new value. If there is a comment or attached file, the client is sent an email indicating as such with the comment sent along in email so the client can read the update.

Tickets go from New to Open, then either to Waiting or Pending, then to Resolved. Sometimes tickets go into “Researching”, “Recurring”, or “Limbo”. The last status, “Limbo” are for those tickets where the situation is beyond waiting, but we still want it to hang around for some reason.

If all of this wasn’t exactly what I was after, the cherry on top is that this theme comes mobile-ready as well. It renders beautifully on an iPhone and iPad, and technically any mobile device as well but those are the only two devices I have to test the site with. Technically anyone can have an account on the site and anyone can submit tickets. I really like how clients are insulated from each other and only see community information in the KB. For admins, it’s all open and available. I really like how that’s structured.

Sometimes clients ignore that we now have SupportPress and elect to get our attention other ways. If they email us, I simply copy the email into a new SupportPress ticket, and set the owner to the person who sent the email. I love that I can create a new ticket on behalf of a client as if they sent it! Any other method of communication that isn’t SupportPress now gets a ticket for each event. If it’s a knock on our door, a ticket. If it’s a phone call, a ticket. If it’s an iChat, a ticket. Everything I do for a client gets a ticket and that way not only do I instantly document everything but the client can see everything about their tickets in one convenient place anytime they wish. They can go into old tickets and see who responded, when, and what they did about the issue. I’ve also started to use the standard blogging features of the WordPress.org site that still exist. SupportPress shuffles that off to the “Blog” menu item. If ever there is something I wish to record, I just send the SupportPress blog an email with the contents of whatever it is I want to record and it ends up being placed in the Blog section. I like to think of that as my “Captains Log” which lets me write odds and ends about the function of my office in one central place. If ever I need to refer back to it, search on it, or print something off of it, there it is. One handy place.

The hosting was inexpensive, the installation of WordPress.org was free and took about seven minutes. The cost of SupportPress was $100 and took about five minutes to install. It took about thirty minutes to set up all the clients and after that we were on the ground running. So for $100 and less than an hour I went from having no help desk infrastructure to having a damn nice one. Nobody has complained and so I count that as votes of approval. Some of my clients have started to adopt SupportPress directly and others have not. I don’t care since I stop people before they get going when it comes to in-your-face interactions to tell them that I first have to create a ticket for them.

I couldn’t imagine going back to the way things were. This is so much more convenient and safe for me in general. It keeps everyone feeling good, feeling honest, and provides a huge amount of CYA if ever a problem of help desk performance should ever pop up. Each ticket contains date and duration stamps which clearly display how each issue was handled. There is no he-said or she-said, there is only the ticket and what it says. Objective, clear, and rational. Again, I couldn’t imagine running a help desk any other way.