Video iPod marks new podcast episodes with the blue dot, just like iTunes does. Unlike iTunes, however, there is no way to keep an episode as new once you've listened to it, nor is there a way to mark an episode as played (so that it gets deleted, for example).

iTunes has this option of deleting podcasts you've listened to ("keep unplayed episodes") - this applies to both audio and video podcasts. However, a "played" podcast in iTunes terminology needs to be listened to the very end - basically played until the iPod itself stops playing it. Since most podcasts have credits (video) / music / clips / etc at the end, the entire episode gets fully played quite rarely. As a result, you have to delete things you've listened to by hand to free up room for upcoming episodes.

The Scala-500 bluetooth headset is pretty cool, it's got the best wind resistance (actually usable outside), light, small and easy to put on with glasses or not. But it has the LARGEST multi-function button out of all the headsets I've seen, and this button CONSTANTLY gets pressed. I have voice dialing set up, and have now made calls to my friends on a number of occasions live from my pocket.

iTunes can automatically download podcasts you subscribe to, providing fresh content on a daily basis. That's all nice and cool, but it really wants to keep a copy for itself. Audio is one thing, but video podcasts, especially long ones, take up quite a bit of space. If you never watch them on iTunes, and just use it as a means of getting stuff onto your iPod, all that space is wasted.

We all have cellphones these days, and all of them have voicemails. Voicemail systems typically have two greetings - one you record, and the instructional one provided by the system. It's the latter that is in most cases way longer than it needs to be - it lists every possible option every time, which is especially frustrating when you just need to leave a quick note and have just waited for 10 rings for the voicemail to kick in.

Those who get their coffee from a deli on the morning commute know this one well. For some reason, the vendors always put napkins on TOP of the coffee cup, effectively rendering them useless - whatever coffee seeps through the lid gets the napkins wet.

Modal dialogs are, unfortunately, quite common in GUI applications. A modal dialog is a dialog (message box, for instance) that blocks the application that popped it until the dialog is closed (answered or dismissed). A variant of a "modal dialog" is a "system-modal dialog", which blocks all applications until the dialog is closed. Fortunately, that one is very rarely used.
So what's wrong with these, you ask? A number of things. Often modal dialogs are used for user-entered information - say, creating a new database record. Information to be entered typically depends on some other information available in the application, but guess what - you can't get to it until you close the dialog. So, you have to close the dialog, find what you need, copy it somewhere else (!!!), and then get back to creating your record. Very convenient, isn't it? It's especially frustrating when the information you need is one dialog below and just needs to be scrolled a little bit - you try, but all you get are error beeps...
That's not all, though - Windows takes it one step further. Under Windows, any application which pops up a modal dialog is automatically brought to the front of all other application windows. Receiving new emails is notorious for this - the "You have new mail" dialog box interrupts whatever you're currently doing, which is especially fun if you're editing a document - whatever you were planning to type in ends up going to the dialog instead of the document.