Yes and I didn't find it makes that much of a difference. Just because my mobile can do email, doesn't mean I like to process email when standing in the middle of the mall. Other contexts are still very relevant in the way they where before. Am I in the city, at work, at home? The @computer-list contains many tasks which assume always-online, but hey, my computer is always online, so what? Sorry, dude, but just don't see the big change here.Has anyone rethought their contexts in the light of the always present always online gadget world we live in today?
The huge, very long @computer-list is best dealt with, I found out for me at least, when you weed it out by getting other GTD-lists up to task. For instance, if I know I should do some of them definitely this week, I "tickle" them instead. That way urgency is taken out of the @computer equation an resides in the Tickler instead.
I am also a very harsh and arrogant pighead towards my someday-maybes. You don't just create a project. And even if I did and then never followed trough, I check my higher-level lists to calibrate my lower-level lists.
I also schedule 1-2 big projects to create a realistic hard-landscape. If it is a given that I need to work on that project 4 hours every day to meet deadline, then that goes into the calendar, 'cos it's real.
All this should lead to an @computer-list that may still be long, but is populated with NAs that truly can wait until you get around to doing them. And thus, I just start to work from the top of that list or choose another one, according to the other 3 criteria.
If I do some @computer tasks and it felt like I wasted my time, this is usually a sign I screwd up at one or more of the aforementioned gatekeepers.