I have read around a few places that [confirmation messages are not the best way to go about warning users](http://www.alistapart.com/articles/neveruseawarning), it's best to let them do whatever they want but give them the option to go back. I thought this probably applies to deleting things a bit, since if you click the button you've decided you want the thing deleted and having to click to confirm is just an extra step (what percentage of users click 'no' on that confirmation screen I wonder...)

I'm working on a web app where the user is managing items in a list. Instead of having a confirmation when the when the user clicks delete, I'm contemplating a couple of different approaches:

1. I was thinking the item goes grey and says [deleted] but there is an
Undo button. Then after several seconds (maybe 6?) the list item
fades out and the items below it move up. (I think it would be
irritating to have them hang around still, because often people want
to get rid of those deleted things and not have to have them hanging
around.)
2. The other approach I thought of having is a 'Recently deleted'
section at the bottom from which things can be restored, and clear
items out after a few days. And in that case have the items just
remove from the list instantly. I'm worried in that case though
that the link between the disappeared list item and the link at the
bottom will not be obvious enough to be intuitive.

The list will likely have its own scrollbar, but it could get quite long.

Do either of these approaches sound reasonable? Is there a better way to avoid having a confirmation message? Or just I just keep the confirmation message?