A better modification of such a statment which I see being used is:
'A company_name employee will never ask for your password'
This message alerts the user that if the person is asking for a password, there is something fishy and he should alert the concerned authorities immediately. With all the live chat functionalities that most industries are providing,...
The three dot symbol is called an 'ellipsis' and has been used in text since at least 1588
Originally it signified a pause or tailing off in speech but, in modern times, it also signifies and implied continuance of any textual content. An example of the modern usage might be in webpages where you sometimes find "More after the jump..." meaning that an ...
People read from left to right and from top to bottom. Chat applications normally place texts from top to bottom. The newest chats placed at the bottom. Placing the input at the bottom, therefore, is logical.
With this answer I didn't mean ALL people. For example, Arabic is read from right to left. But considering this websites' audience and the OPs ...
placeholder="Enter your next post here!">
<textarea name="postText" rows="3"
to put the input at the
it would make sense
from bottom to top,
read a chat window
In a world where we
MSN Messenger Service
How do you feel about the typing indicator—“David is typing”—that
appears on your buddy’s screen while you’re composing a message in
chat? Does it make you feel self-conscious about how long you’re
taking to write a message? Do you hate it when you are multitasking and your erstwhile best friend keeps sending messages like “...
Most security breaches are from social engineering, and so telling someone that they should never under any circumstances give anyone their password is an attempt to increase security. I would suggest a statement more like:
If anyone asks you for your password, you should assume they are a criminal and report it immediately!
Idea provided by @Kaz
As a ...
Think about what it means to be staring at that loading spinner:
The user doesn’t want to do any of this. He has no interest in managing his utilities. It’s something he might have to do from time to time, but he’s hardly happy about it. This had better be a smooth experience.
The system has failed. Few people go straight to support without a problem ...
If you look at most languages they are from left to right and the basic concept of a chat is about mutual interaction based upon the person's previous response. Hence, your responses will be driven by the response of your chat partner and hence his response is placed on the left and your response on the right since your response is driven by what he has said....
Of the two options you have given, the second one is the best, as it's more visually obvious where the message starts. Hence it is easier to use as people have to think less about the structure of the message and can focus more on the content. It can however prove problematic if you have some long names in the chat, so you will likely have to come up with ...
Scenario: Your friend's messenger has 'virus' and is sending messages to his contacts. You mark his virus's message as spam.
Do you want this to also block your friend?
Or, do you just want to mark his message as spam?
You see, there are times when you just want to mark a message as spam since it is coming from a known contact.
Ignoring an user should ...
I'd say yes, absolutely.
When presented with a larger box, the visual implication is that the text ought to be longer and well thought-out.
Take this site we're on now as an example. We're meant to type out researched, thoughtful replies that may very well be several paragraphs long. The initial box is sized to fit several paragraphs to encourage this. ...
I don't see it as more than logical.
If the text is displayed in the main window from top to bottom, then the input box for your reply is on the bottom, because that's where your text will end up.
While in another situation, like a comment thread on a blog, the most recent entry can be on top.
Then the input field for new entries is above that, again, ...
The evils of the modern information age.
Chat programs, e-mail programs, and most non-SSL web pages transfer information back and forth in a clear text format. This means that it's non-encrypted and readable by anyone with access to the text.
Even though the network your computer is connected to seems like a physical straight connection to the router or ...
It's a practice perpetuated by corporate legal counsel and made somewhat necessary by our litigious society. It is silly and slightly insulting but, fortunately, we all do it so we all look equally insulting.
I think it ties into the usability heuristic of always showing the user the status of the system. If someone on the other end is typing, that's an update to the person who is waiting.
Now if it's not really happening, that seems to be something of a dark pattern to keep the user engaged on the site vs. letting them get back to what they were doing and ...
Marking a message as spam and blocking a have different use cases.
Spam is generic content that is sent to many people (usually advertising). The goal of marking something as spam is to let your system intelligently remove other identical (or similar) posts so that other members don't have to be presented with this. Gmail does an excellent job of this.
I would say it depends on the use case you are looking at and how the closing of the chat affects the conversation. For example, If I am chatting with AT&T customer care on their web chat and if either one of us closes the chat, the chat gets disconnected and hence a notification is very useful.
However if you are designing a chat messenger like say ...
When multiple messages are ordered in order of writing, it is natural to put the latest one at the bottom. This mimics how physical writing works - imagine a long paper sheet or a guestbook where people come by from time to time and leave a note.
Everyone would write their note just under the last note, and it would end up automatically ordered from oldest ...
I would strongly recommend that you store your chat history since a simple search for " Chat History in Google" you see that its a feature a lot of people request for in chat clients.
It would be amazing if you could have all of your chat history(and
other history such as emails, file transfers, tweets, etc) all saved
online so that ...
Why do you think its a bad user experience, Just because you feel the alignment between the lines gets disturbed doesnt mean its a poor user experience. Check with your user base and find out if they find these smileys useful and then make the decision. What might seem as a irrelevant and bad add-on might not be a bad user experience for users.
A quick ...
The reason is not related to any language but the nature of the information and the focusing point for getting a general overview of changing any situation.
Conversation is not a static information like the text in book. Placing text on the bottom will let user to get the latest message and ongoing conversation.
The computer console is also working with ...
Always give users control
Our inboxes are overloaded as it is. You're right to worry. You have to provide notification for those who come and go, but you can't force on the regulars or people who end up linked to a popular discussion.
Stack Exchange provides a good pattern
A checkbox to activate email subscription:
And in-line settings to control ...
Allow the users to choose
If you want to maintain the conversation as the same thread, you could provide the users with the option at the time of invitation.
download bmml source – Wireframes created with Balsamiq Mockups
To me, choosing not to share is essentially the same as creating a new conversation with the additional user.
This will ...
You should consider the ramifications behind allowing someone to delete a message in context and base your decision on that.
If you allow someone to delete a message and don’t provide all possible observers of the message log a way of knowing that the message log was altered, you are opening the log up to abuse.
User A could bait User B into posting ...
2 approaches I like:
1st (eg: adium messenger):
Name in first line
Message starts from new line
2nd one (eg: facebook chat):
Just use icon to show user thumbnail (show username in window title)
Just show messages.
For a chat room scenario: I would go with what we have here on SEs. Right align usernames and left align text inside respective ...
Where I work management wants it to be a popup.
Everyone will probably vote this down by the way. But I've tested in the header, in the footer, inline with copy on product pages. etc.
It's sad but I think chat is only good for personas that expect to have a popup or chat and then have their hand-holded throughout the buying experience.
It also doesn't ...
The web app I am working on has a floating triangular chat/feedback button that persists in the bottom right corner no matter where the user scrolls. It gets in the way and many users are accidentally clicking it when trying to use the scroll bar, so I would not recommend that.
A much better placement (assuming you want visitors to chat, and you're not ...
I am on the "support everything" side. You see, many times a user wants support, he does not need a technical solution so much as he needs somebody to hold his hand and tell him that everything will be OK.
Promising support is a factor in user satisfaction, even if people never happen to use it - they just feel better knowing that, if they need help, there ...
English speakers read from top to bottom.
In order to comment on a Discussion, it is advisable to read the conversation before commenting.
By placing the conversation before the input field, we increase the likely-hood that users read before commenting.
In some websites, it is the opposite - The input field is first, then the most popular comment is after ...