I probably should have pointed it out. I've added a footnote. Writing blog posts like these is a balancing act. On the one hand, I want to keep it short and st

I probably should have pointed it out. I've added a footnote. Writing blog posts like these is a balancing act. On the one hand, I want to keep it short and stick to the point I'm making. The fact that you can get a refund is not directly related to the specific UI problem I'm describing, just like the "undo" feature in a desktop application isn't directly related to, say, mislabeled menu entries. On the other hand, I try to write defensively. If an article is read by hundreds or thousands of people, there will inevitable be some people who feel that something they consider important was not included. I try to anticipate the most obvious criticisms or questions, and explicitly mention them preventively. But if I include all of them, the text will eventually become unreadable. I'm also writing for an audience of UI designers, who generally realize that I'm merely pointing out specific UI flaws, rather than making larger points about the products or companies I use as examples. I probably missed the mark by not pointing out the fact that it's possible to get refunds, but I think it's not as obvious as you imply.