It all started with this

Micromanging your Phone

When queried, the gentleman said the phone hadn’t gotten wet, and it was fully charged, and he was not aware of how to reboot the device. The sales associate plugged the phone into a dock cable (apparently it was very low on power), and the phone responded just fine. He then proceeded to, without any further investigation, tell the gentleman the problem. “You’ve got too many apps running. You have to double tap the home button to bring up the task manager, then tap and hold on an app to make them wiggle, then tap to kill them. You’ve got to kill your apps when you’re not using them, or the system will get full and freeze up.”

I was very shocked to hear this, because I actually know how iOS manages its memory and processing power. Clearly this sales associate didn’t have a clue. I tweeted and walked away amused, only to have a very long twitter conversation with a friend about this issue. Apparently he had been told the same thing, but by a genius. To make matters worse, he had shared the knowledge of how to kill tasks (which by design is pretty difficult to stumble upon) with a friend of his. This friend now runs an app, and when he’s done, immediately kills it. Every single app, every single time. I was just flabbergasted.

I mean, I kill apps myself, but only in one specific instance: if the app has frozen and its quicker to kill it and restart than wait for iOS to decide its had enough and perform the kill itself. The thing is, I know what I’m doing. I would never tell a normal user how to kill their apps, unless I also included a hefty educational speech about when and why you do this. In everyday usage, nobody should have to do it, period. Even those rare instances should be infrequent enough that the average user doesn’t encounter it. Having a user forced to manage what apps are running strikes me as straying far into Android territory. If iOS is failing so badly at memory management that the everyday user is forced to manage running processes, why not add in an activity monitor app so I can see memory and CPU usage while I’m at it.

The Problem is Getting Attention

I spent some time poking around the dark corners of the internet, and there were plenty of confused normals spouting this “kill your apps manually” nonsense. To make matters worse, the people who knew better came off as condescending when trying to correct the normals, and every thread I found just devolved into name calling. I didn’t feel up to wading into the mess, so I made sure to educate my relatives, then let sleeping dogs lie. Fast forward a few months, and the problem is getting a little attention, at least in certain circles.

It started with Speirs, got picked up by Gruber. Then Speirs went and documented the whole process on video, which in my mind should lay to rest this issue, at least for anybody willing to watch the video in its entirety.

Who is To Blame?

The thing is that really bothers me is, how exactly are “normals” getting educated about the app kill functionality? I’m not sure, but my best guess is word of mouth many times removed, eventually traced back to uninformed apple employees or know it all children.

Clearly Apple needs to include the app kill method as part of their employee training, and make sure their employees know what it does and does not accomplish. That would at least stop the misinformation at the source.

I know Apple would be happy if most users never knew about the app kill functionality, and perhaps its best that way. However, in order to clean up the mess made by their well intentioned employees, consumers need to be educated on the facts, at least on a case by case basis. People who overuse the app kill functionality are wasting massive amounts of their time, and this needs to be stopped.

The Rise of the Syncing Services

Eventually I stumbled upon a service called SugarSync, and I fell in love. I was able to specify certain folders, and these folders would automagically stay in sync across multiple computers and multiple OSs, without effort. I even had access to the files through a website.

I set up a client with SugarSync to mirror their documents to several business computers, and used a script to make backup copies of critical files, which are then backed up to the web via SugarSync. Coupled with its file versioning support, it has on more than one occasion allowed me to recover files and undo drastic mistakes that would have otherwise crippled the business.

I ended up getting into an invite-only service called Dropbox not long before it went public, and to date it is my primary solution to the remote access problem. I still maintain SSH server and remote desktop access to my desktop, but I almost never need to bother.

My roommate recently had her notebook stolen, and was rather devastated. She’s starting a new business, and one of the lost files was the most recent copy of her business plan. She asked me to OCR an older copy she had lying around, and I was a little confused; I had set her up with Dropbox several months prior, and I don’t think she fully understood the benefits. Sure enough, all of her files were fine, safely mirrored to her old desktop and the web.

While these services are highly useful, they have yet to hit the mainstream. Both Microsoft and Apple have their own competing versions, and moving forward we’re going to see this kind of sync become a key part of the computing experience. Already you can log into your online photo gallery or email account from anywhere and have access to all your data. Eventually all of your files will be stored in the cloud, and will be automatically accessed by any device you own. You’ll be able to log onto a friend’s computer, and all of your files, applications, and settings will be the same as if you were using your own computer.

I don’t see computers all becoming dumb terminals like the early days of computing, but the effect will be much the same. It will no longer matter if we’re using a tablet, phone, desktop, or laptop. It will no longer matter where we are, or who owns the device we’re using. We’ll no longer be constrained to any particular device or location to accomplish our tasks.

There are programs out there that allow you to customize your systemwide gestures, but I’ve always been kind of a purist when it comes to input solutions. I’d rather learn to use what ‘the masses’ use, so I’m equally at home on someone’s stock install as I am on my highly customized one. Recent self discovery has made me rethink my position a bit, but I digress.

Up or Down

With the release of OSX Lion, millions of people are quickly discovering that scrolling with the trackpad doesn’t work like it used to. In fact, it works opposite. Years of scrolling with the touchpad, in multiple OSs, has taught us that dragging your fingers top to bottom should scroll the page down, and dragging your fingers bottom to top should scroll the page up. Amusingly, on all iOS devices, the opposite is true. With a touchscreen, you grab and drag the page with your finger. Thus, dragging bottom to top scrolls the page down by pushing the content up and off the screen. Apple has decided to force this scrolling paradigm on its OSX users, and I can’t say I disagree with them. Honestly it takes all of a day to get used to the new direction; Your brain is quick to adapt.

The exception, of course, is if you have to use another computer: An older copy of OSX, or a Windows machine where the scroll directions are now ‘backwards’. Your brain can compensate with a little difficulty, but its confusing to go back and forth every day. The simple solution is to swap your Mac to match the Windows default, but this causes problems moving forward. If you spend a lot of time working on different Macs, you’re going to spend a lot of time being annoyed with the scroll direction. You can of course change the Windows scroll direction to match the Mac default, but you’re going to have the same problems if you end up working on a lot of different Windows machines. The best solution (other than waiting for Microsoft to mirror Apple’s change, or waiting for Apple to capitulate and change back), is to just pick what world you spend most of your time in, and set your scroll directions to give you the least amount of change.

My roommate had this very problem, but was unable to change his Windows scroll direction. His mouse driver didn’t support it, and he lacked the registry access necessary to flip the proper bit. I wrote a fix for him in my head a few seconds after he complained about it:

WheelDown::WheelUp
WheelUp::WheelDown

Running this script in AutoHotkey reverses the scroll direction for almost all cases (ignoring a few games that grab low level mouse input).

Backwards or Forwards

In addition to the scroll direction changes, OSX also changed the default forward/backwards direction for webpages in Safari. Before, three fingers right to left would go backwards a page, and three fingers left to right would move you forward a page. Now, two fingers right to left moves you forward a page (by pushing the old page offscreen), and two fingers left to right moves you backwards a page. My big problem here is with Apple’s Finder application. Two finger forward/backwards does not work, and instead scrolls around the content in the window. Honestly, this is exactly what I want and would expect, but it breaks rank with Safari.

Two Fingers or Three

To make matters even more confusing, there is an option to enable the old 3 finger scrolling gesture, which then allows Finder and Safari to both support 3 finger scrolling in the same direction: the old one. Apparently 3 finger scrolling ignores the systemwide scroll reversal option. There’s also a 2 and 3 finger option that allows you to use both gestures, but it ends up being an ungainly mess. You end up scrolling backwards with 3 fingers, forwards with 2.

Consistency

Honestly I’m not sure what they were thinking here. Consistency is one thing I value highly, and this is anything but. For now, I’ve accepted reverse up/down scrolling, but I’ve kept backwards left/right 3 finger scrolling. A mess to be sure, but its the smallest mess I could make.

The default OSX Terminal application is a great little program, with plenty of features. It even comes with a selection of themes to style the look and feel of the app, and years ago I may have just changed to the Pro theme and been done with it. However, I’ve long since developed my own terminal theme, very similar to the IR_Black theme. I have some mild look and feel differences, and I’ve altered the keybindings to more closely mirror what happens in the rest of the OS. In addition to this, I also copy over a .bash_profile with some useful settings (prompt colors, aliases for ls variants), a .vimrc file with some minor tweaks, and a .inputrc file to help with keybindings. In particular, standardized keybindings for home/end and pgup/pgdown are necessary to preserve my sanity at the command line (yay laptop keyboards).

Only after this ritual is complete can I really settle down and get any sort of command line work done. Some day in the distant future, perhaps someone else besides me will launch the terminal on this laptop and say a little prayer of thanks.

An Easier Way

I’m still a bit crazy about missing news, but thankfully RSS has at least made this process manageable. It amuses me to no end that the average user has no idea that this technology exists, despite the fact that it is used so widely. That said, not every page puts out a feed. Sometimes they do publish one, but its riddled with information you don’t want: Occasional advertisements, rants about off-topic issues, and other information that doesn’t interest you. While stumbling my way to a solution for this problem, I discovered Yahoo Pipes.

Imagine if you could take a source of information, anything from a webpage to a CSV file, and filter out what you don’t want. The resulting data can then be merged with another data source, and then republished as a single new data source. With Yahoo Pipes, you can do exactly this.

Tor doesn’t offer feeds for its authors, so I my first pipe took their master feed and filtered by the author I wanted. I created a pipe to filtered out a friend’s blog posts from a collaborative site. I made a pipe to watch the price change feed for appshopper.com, and filter out only applications I was interested in buying. I even made a pipe that takes a calendar and strips out events I don’t want to attend. You can take most any published data as input, transform and combine it at will, and output it in whatever format you desire. It isn’t exactly the most user friendly of tools, but its got enough power to make up for that.

Overlap

There’s a serious amount of overlap in my feeds; I’ll read about news from its original source, from someone reporting on that source, from someone reporting twice removed, and then it’ll hit mainstream media, and I’ll read about it 10x over the next few weeks as it gets repeated. I like knowing about bleeding edge technology news before the mainstream media does. Often I’ll hear about things days or weeks before they hit CNN. Often rather than follow a pundit and read the news he puts out, I’ll go straight to his sources and follow them instead. I have to constantly prune my sources, lest I become overwhelmed. Do I want to read information from sources that are among the first to report it, or would I rathe read a more critical analysis from a site that reports thirdhand a few days later? Often the best choice still involves some level of overlap.

Filtering

I’ve tried to create pipes to handle this overlap, but its not easy. Assuming two sites publish a story and use the same title, the stories are easily matched and one can be discarded. This rarely happens. Even using lots of metadata (author, source link, rough date/time, categories), its a beast of a matching problem and difficult to do consistently. Also, there’s the problem of comments, which offer actual useful information from time to time. If you discard one article, you lose the comments of all the other duplicate articles.

Clearly this issue needs to be handled at a higher level than pipes was intended to solve. The underlying data to solve this problem is there. Most reputable sites link back to their sources. Brute force comparison of articles can easily establish if they’re discussing the same topic. I want an engine that sees all news from all sources, and groups them together by common threads. For critical topics, an actual person could serve to quickly make links between related stories.

As a story develops, additional sources and comments can be added to the aggregate news source. If I read about a product, and it is mentioned a dozen times over the course of the next month, with each source offering no new information, I shouldn’t have to see any of the duplicate articles. If these new sources offer actual new information, or a decent amount of analysis, I’d like the information to be merged with the original story, and the story marked as updated with new information. No matter what site you visit to learn about a news story, you should be able to easily link to the master source of all news on that story.

Someday soon I hope to have my overlap handled automatically and seamlessly. Perhaps then I’ll free up a few more minutes each day to do something besides reading. Then again, perhaps I’ll just broaden my horizons and start reading new topics.

Update 9/2011

A tool far less powerful than pipes, but quite interesting, has cropped up recently: ifft.com. You can use recipes which allow you to have triggered actions happen on pre-specified events. It has only a small overlap with pipes in terms of functional uses, but you can do some interesting things with it. Feeds can be created from every post you star in Twitter. Instagram pictures can auto save to your Dropbox. Checking in on Foursquare can trigger a Facebook status change. A text message can be sent if the weather report says its going to rain. If someone tags you in a picture in Facebook, you can have the picture emailed to your mom. I’ve found ways to use this service to complement pipes, by creating quick and easy to use data sources that pipes can then work with.

There is no worse sin for an OS than to let an application take control of my focus. Nothing is quite like the exquisite torment of being in the middle of giving your program commands, and nothing happens. Perhaps another program popped up in a second window when I wasn’t looking and took focus from me. Sometimes I launch a program, then switch to a web browser and start navigating, only to have my focus is lost to a modal popup. I switch back to the web browser, continue navigating, and the same app opens another modal popup, breaking up my browsing experience yet again.

Seriously, I’m trying to get some work done here. I swapped away from your slow, bloated program, because it takes 20 seconds to fully launch. I don’t want to sit there wasting time while you finish. Just do your load, and don’t steal my focus, is that so hard?

Besides being horribly annoying, its been known to cause serious problems for people. My personal low involved me setting my away message in my messaging program to my banking website password for two days. Currently most of the onus of this problem is on the application developer, but I think that’s just passing the buck. OS developers need to make a stand and put in place protections to prevent this sort of thing.

This time I babysit iTunes through all the steps in sequence, though this time there’s an extra step 4 in there (unsure how that happened).

Ideas

I know you have some UX guys working for you Apple; Perhaps you could throw them at this problem for a while? My thoughts:

• Make iTunes more responsive. I kept tasking out because of the huge lag between clicking OK and actual things happening.
• Keep my apps up to date, automatically, in the background. At least make it an option. And please, delta sync.
• Get rid of the age restricted warnings. Ask me once, per account (or even per app), and that’s it. Never ask me again.
• Remember where I am. If the user happens to sit at the Enter password to continue box for 10 minutes, comes back, and clicks OK… continue with what they asked you to do 10 minutes ago, don’t just sit there.

Its my sincere hope that somewhere deep in the bowels of Apple, there’s a skunkworks team that has spent years rewriting iTunes from the ground up. Its responsive, easy to use, performs simple tasks with little to no effort, and doesn’t require holding down option to delete a song from within a smart playlist. Any day now, it’ll drop. Please.

Not Just Microsoft

Microsoft isn’t the only company guilty of misusing this folder, and it doesn’t just happen on OSX. Back when I was in pc-land, I remember games trying to constantly take over my Documents folder to store not just game saves, but all sorts of settings (log files, downloaded maps, configuration files, etc).

This problem is apparently persisting to this day, as the recent Starcraft 2 Beta puts a nice fat Blizzard folder in Documents, storing maps, replays, campaign progress, system information, graphics settings. Steam just launched for the Mac, and lo and behold, I’ve got this silly Steam Content folder in my Documents. Thanks guys! I really wanted every game I download via Steam to be stuck here.

Some of the tricks I discovered for Office work equally well for these other offenders. Sometimes its just easier to set up exceptions for these folders in my syncing process. Other times I’ll just uninstall the software making a mess, especially if I don’t need to use it often. I’ve been sorely tempted to move all of my actual documents to a completely different folder, but that would irk me to no end.

Update 10/2011

Blizzard was nice enough to move the offending files out of the Documents folder and into the Library folder in this patch.

When you pull out your iPod and hit the Knit Buddy button to manage your needles and yarn, that’s what we call an “app”. Now, let’s say you’re at the yarn store and you need to access your yarn and needle inventory to figure out what you need to buy for your latest creation. You realize you forgot your iPod at home. There’s no easy way to get access to the information you stored there. You could drive home and get your iPod, but it’s a long way. You could call Grandpa and attempt to have him look up the information, but what if he’s napping, or has the TV turned up too loud again? What if you could access your knitting inventory from your iPod, or your friends phone, or by the store’s computer? That’s what we call a “web app”. Instead of being stuck running an “app” on a single device, and having your information locked to that device, you run a “web app” on any device attached to the web, and you can access your information anywhere.

Now I did take a little poetic license here, and I assumed that my grandmother at least understood what an iPod and the internet were. Who knows; if she had lived a little longer, I may have gotten around to explaining them to her.

In any event, while I didn’t win the grand prize, I did have my entry published.

Common Reasons For Removal

• The content of the page becomes outdated, and is removed entirely.
• The website is redesigned, and old information is moved to an entirely new location
• The type of information changes (a pdf becomes a web page)
• Static content becomes dynamic

Coping With The Problem

There are a few basic ways to cope with out of date URLs. You can display a custom 404 error, perhaps with a search box to allow the user to more easily find the page he was looking for. You can redirect the user back to the root of your website, and hope they can find their way from there. Ideally, you can configure your web-server to redirect all requests from the old URL to the new URL. Unfortunately, the latter process can become quite unwieldy, and is often just ignored, especially on larger websites and over long time periods.

The best solution is to plan ahead when first launching your website. With proper planning, you can configure your website’s URL structure to cope with changes in underlying design and technology without changing the basic URL structure.

If a piece of content is going to be advertised or linked to, its URL should be a folder. example.com/resume is far preferable to example.com/resume.htm or example.com/resume/resume.pdf.

If your website is highly dynamic, generating content on the fly, then your URL structure is even more critical. example.com/home.php?page=intro&lang=en&spash=yes is confusing, and painful to type by hand. example.com/intro is simple and easy to type.

How I Handle It

Everybody seems to have their own opinions on how to set up your blog with permanent links. The main concerns seem to be SEO, which isn’t terribly important to me, but I took it into account. I’ve never had a lot of publicly accessible links on my website, so there weren’t many links to preserve. I did choose to maintain most of the hosted files and private content, as I’d planned for that ages ago.

I settled on this structure: http://curtistasker.com/blog/%category%/%post_id%/%posttitle%. I wanted the word ‘blog’ in the url somewhere, to indicate at a glance (and to search engines) that this was a blog post. I plan on using a small number of categories with little overlap, so having the category in the URL is reasonable. It provides an additional keyword for search engines, and offers users a bit more information to go along with the post title. Post ID is there mostly to make search engines happy, as quite a few people seemed to think a three or more digit numeric in your URL was beneficial. And finally it closes with the post title.

Tweaking WordPress to handle this structure wasn’t terribly bad, though its since gotten easier. I’ve been able to get rid of a custom plugin I wrote to handle category links, as newer versions of WordPress can handle what I want by default. I also use a lot URL Rewriting to help prevent duplicate links, by forcing www.example.com/file1 and example.com/file1 and example.com/files/file1 to all redirect to the same URL. I also discourage duplicate indexing of content (category and tag pages with summaries).