The computer world is the one that limited these concepts.
Before web: you can only copy and give.
After web: you can give, or publish.
After cloud: you can give, publish, and share.
I think these concepts should be as well differentiated in the digital world as they are in the physical.
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.
Yep, they are. It's impossible to share digital data without making a copy that is not under your control. There are some difference in write permissions, but people also do understand those.
"Sharing" with a group of people like in Facebook (where each one can essentially change the nature of the thing in real time by commenting on it or liking it) is also somewhat distinct from the other two because it makes a send-time copy that can be changed (in limited ways) by people other than you in possibly unpredictable ways.
Now shareD as a state is how the metaphor makes sense, for content stored at a common resource where one can take it back later, like your profile on a social network. So a better use that would hold the right nuances would be:
- Publish for making copies of the content and sending them to channels where one doesn't have control.
- Shared / Private for the status of content on channels on which you keep control to change that status.
Unfortunately, the needs of social sites (that try to make as much shared information as possible, and avoid people to withdraw it) have promoted the current confusing usage and spoiled it for all.
A social network or blog does not. They're objects that are shared.
Using separate icons for "share" vs "send" would make sense to users.
I'm thinking some kind of "upload" metaphor vs "message" metaphor is right. Messaging metaphors are easy, but upload is a bit more tricky... Apple might have the right idea - but Apple's "out of box" icon is too vague, obviously because of Apple's need to keep icons elegantly simple. I'd go for a bit more complexity:
An arrow pointing at a globe. When you share something, you share with the internet. MS Office used globes to represent the Web - like a chain+globe for a hyperlink and whatnot. Use that - an arrow at the globe implies you're sending something to the Internet (and generally a public or semi-public place on the Web specifically).
(The second and third sections are what can now be extended by developers in iOS 8.)
Including : * Printing the document * Viewing a video on my TV * Mailing it * Marking it to Read Later * Copying the URL * etc...
technically it's more a "Send to another application"
Which I think is actually kind of ok, because again not everything has a simple obvious icon. Some things might be better served with just standardizing on an abstract and distinct shape. Newcomers may not know what a floppy disk is but they will learn the association anyway. And it just becomes one of those cool bits of lore that nerds like, double win!
If I "share" via e-mail, then I transmit a document to others. After this, each recipient has a separate copy which, thereafter, is completely out of my control.
If I "share" via social network, then I upload a document. This makes a single copy, accessible to previously chosen people. It is (depending on the social network) somewhat under my control. Others can comment on it.
If I "share" via something like Dropbox, then I make the document accessible to others. No copy is made. If I share via URL, then I give read access. If I make a shared folder, then I give both read and write access.
Now, we techies know these are different things. Our mental model of non-technical users' thinking might suggest that, to them, these are all the same kind of action.
But are they?
Does an average non-technical user think of folder sharing, Facebook posts, and e-mail messages as the same category of action? I'm not sure he does.