Facebook announces new Messaging Feature
blog.facebook.com
blog.facebook.com
“All of your messages with someone will be together in one place, whether they are sent over chat, email or SMS. You can see everything you’ve discussed with each friend as a single conversation.
I’m intensely jealous of the next generation who will have something like Facebook for their whole lives. They will have the conversational history with the people in their lives all the way back to the beginning: From “hey nice to meet you” to “do you want to get coffee sometime” to “our kids have soccer practice at 6 pm tonight.” That’s a really cool idea.”
I bet advertisers (Facebook's true customers, let's not forget), overzealous law enforcement officials, not-so-honest-or-nice politicians, and identity thieves, are also intensely jealous of future generations with access to entire records of conversations.
As will Facebook. What a terrible thought.
Somewhat like Google+Schmidt.
Email is an open distributed platform where everyone can set up their own mail servers and have control of their own mail. There are tens or hundreds of thousands of email systems out there. To replace that with a system whereby one company has complete control of your messages? Bad.
This seems to me to be a long overdue and obvious overhaul of their crufty messaging system based on the realization that many people actually do not use e-mail anymore and rely instead on Facebook’s woefully inadequate messaging tools.
To me, an email is basically an email address.
IMO "email" is a combination of the various transport technologies and the message format.
The good news is that lots of people are going to be able to send and receive email messages using email adresses.
Both these messages and adresses are rfc2821 compliant.
By Metcalfe's law, this can only increase the value of the email network.
Remember, first AOL was an island, then AOL offered an email gateway, and soon enough AOL became irrelevant.
I don't know if the same is going to happen with Facebook, but if it happens, I won't be surprised, for Facebook is like a second wave AOL, a much bigger wave than the first one, because this time it's like "everybody" participates, not just the early adopters.
+ It incorporates existing modes of communication. You HAD to have a Wave account to talk to someone else on Wave, and the biggest issue for me when I got my account was that I didn't have anyone to use Wave with. Facebook doesn't particularly care in this case, it wants to aggregate ALL your communication. You'll stay in touch with your less techy friends who still email you or text you.
+ Large user base with existing friends list. Google Wave started you out from scratch.
+ Really smart product video. Most people didn't want to watch the Google Wave video or got confused by it, whereas Facebook's video is super clear about what it is. It focuses less on the cool tech (unlike Google Wave) and focuses completely on why you will want to use it.
"Today I'm excited to announce the next evolution of Messages. You decide how you want to talk to your friends: via SMS, chat, email or Messages. They will receive your message through whatever medium or device is convenient for them, and you can both have a conversation in real time. You shouldn't have to remember who prefers IM over email or worry about which technology to use. Simply choose their name and type a message."
But the simple ability to sort personal messages from mass bacn is still the #1 feature I've wanted from Facebook, through all these years of feed redesigns and app platforms.
Wave failed because it had no interface to existing services. From that facebook blog post, it looks to me like facebook messages will have "transports" to email, IM (icq, aim, jabber, ...?), phone/SMS.
That's important. Really important. That way, there's no way you "lose" your friends by adapting the new system. You can still reach them!
I'd love to have a seamless experience between ...
* short urgent messages (SMS) * short low-priority messages (IM) * long messages (email)
facebook messages promises that. i'm tempted to see for myself.
Wave took something that worked and made it worse -- fewer contacts, bloated app, confusing purpose.
FB is taking something that works and making it better (for its users) -- more streamlined (like chat), less hassle (existing friends list), less noise ('Other' bin).
They're down as the picture for Chris Piro.
Apologies for those uninterested in 80s and 90s UK kids entertainment, but it just seems so random.
Is that it requires users to do something different than they expect or do currently. The goal of having a "unified inbox" won't work unless you natively integrate with all the places where somebody currently sends messages. This requires the user to change their behavior for what? To have a "unified inbox?" I don't think that's compelling enough for user to change their messaging behavior.
Google has the same issue with Google Voice.
Yes, it'll be easier. But I, for one, won't use Facebook Messages for SMS. Why would I text Facebook to text my buddy for me? When I can just select him from my address book?
All of a sudden the idea of unified communications and messaging is out the window.
Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
Even Facebook seem to have caught the email is dead meme.
"keep this lookup table in my head"
Is this a pain point for anyone? Our contacts are stored in such a way that this is obvious, I can't send a SMS to grandma as she doesn't have a mobile.
Yes, I have several friends whose SMS, Facebook, and email contacts I have but who each prefer a different service.
If I tell my friends to find me at facebook/kilimanjaro I want them to message me at kilimanjaro@facebook.com too.
They should associate and create 500M email accounts right away and become the greatest email provider on earth.
I don't remember hearing if you can add some one to an existing conversation. But I clearly remember that they said that it was possible to remove some one from a conversation. Therefore, I assume, that they would have also thought of adding a person.
The world of asynchronous and synchronous communication is going to clash in a very messy, destructive, apocalyptic Neo-versus-Agent Smith way.
For example:
1. SMS
When I send a message via SMS, it could be either to pass on information or initiate (continue) a conversation. Sometimes the content of the message isn't clear enough to highlight the context and when this happens between a boyfriend and girlfriend, the gates of hell can be opened, and the fury of a thousand suns going supernova is unleashed, usually on the hapless boyfriend (not a true story, I swear).
Or whether you should end the thread with 'ttys' or 'ttyl' or 'brb' as with IM protocol, and trust me, sometimes not continuing a SMS thread or not ending it nicely can lead to you having to spend money to say sorry.
Although I think SMS usage has been happening long enough that people generally tend to interpret context relatively well NOW, SMS communication sometimes do suffer from the problem of parties not knowing whether a conversation is supposed to be happening asynchronously or (relatively) synchronously.
If you have ever sent an SMS (usually to an attractive member of the opposite sex after a first meeting, or maybe a very prospective business contact) and waited for a few hours for a reply, frantically wondering if you had said something wrong, or that person wasn't interested in maintaining what looked like a blossoming relationship, then you understand how different perceptions of what mode a conversation is supposed to be in can sunder the social fabric.
2. Email
We tend to allow the intervals between subsequent emails in a conversation to be longer than SMS. After all, there is the general understanding that accessing and replying to one's email is harder than receiving and sending messages via SMS because of the ubiquity of the mobile phone versus Internet access on the move and the ease of entering a long form email versus sending a SMS. Also, it is easier for most to type long message when emailing than when sending a SMS due to the nature of the clients and where we actually do it (i.e. on the desktop). I usually switch to a more focused mode when reading emails because they generally are about work and are usually longer.
Subject headers in email are a great way to delineate threads. An email with a new subject is the start of a new thread.
3. Instant messaging
Instant messaging is clearly generally expected to be synchronous. When instant messaging, there are socially acceptable standards to start and end a conversation. The signaling has been learned.
Is it going to be impossible to learn the new social rules of engagement? I don't believe it will be so. However, I do believe that the lack of clear signaling of the context of a conversation (i.e. synchronous versus asynchronous, start of a new topic ...) could be disastrous.
Note: Maybe only some of us have to relearn. It could very well be the younger generation already know how to contextualize the messages without use of the various channels, subject headers ... If so, I'm curious how they do it.