I agree with what you are saying. Read my comment below.
Expanding on that, and with the clear examples you gave, maybe the thing is that traditional or classic icons pictures the channel where the information was traveling and not the action itself.
A fax icon implies sending a document because everyone knows that a fax can only send documents. So the icon is representing the channel.
Same for the envelope icon with email (or even snail mail). It pictures the channel, not the action.
If you see a group of icons, one with the Facebook icon, one with Reddit's, one with Slashdot's, etc, you automatically know that it has to do with that particular channel, even if the action per se might not be clear enough, e.g. if I click the Facebook icon, what action am I taking? am I uploading/sending/sharing/pasting/chatting/emailing?
I don't care, I only care that the channel is the correct one. The service that administers that channel is the responsible one for doing what the user expects.
So maybe a fundamental flaw, like you say, is that different actions represent different channels but we are trying to put actions AND channels under a single umbrella, then there's no surprise that you can find lots of edge cases where the idea doesn't apply.
Expanding on that, and with the clear examples you gave, maybe the thing is that traditional or classic icons pictures the channel where the information was traveling and not the action itself.
A fax icon implies sending a document because everyone knows that a fax can only send documents. So the icon is representing the channel.
Same for the envelope icon with email (or even snail mail). It pictures the channel, not the action.
If you see a group of icons, one with the Facebook icon, one with Reddit's, one with Slashdot's, etc, you automatically know that it has to do with that particular channel, even if the action per se might not be clear enough, e.g. if I click the Facebook icon, what action am I taking? am I uploading/sending/sharing/pasting/chatting/emailing?
I don't care, I only care that the channel is the correct one. The service that administers that channel is the responsible one for doing what the user expects.
So maybe a fundamental flaw, like you say, is that different actions represent different channels but we are trying to put actions AND channels under a single umbrella, then there's no surprise that you can find lots of edge cases where the idea doesn't apply.