消息和聊天区别混淆

当我想要访问我大脑标记为“讨论”的与其他成员的交流时,我总是迷路/感到困惑。这些讨论有些是通过聊天进行的,有些是通过私信进行的。我进入聊天,找不到,然后才意识到那一定是一条私信,私信在哪里来着?哦,对了,我需要点击右上角的头像才能找到它们……

说实话,这很令人困惑。这些互动的第一个特点是它们是与一个人(或一小群人)在封闭空间内进行的。媒介(聊天或消息)对我来说并不那么突出:当然,我完全理解它们之间的区别,但在实践中,由于我习惯于为了个人/私密互动而进入聊天,所以我一直“找不到”我的消息。聊天和消息之间的区别主要在于互动的速度(这取决于你看待事物的方式,驱动或被驱动着话语的长度),但有时人们不会立即回复聊天,或者会立即回复私信。

别误会,我喜欢两者都有。但它们被分开的方式,私信试图成为某种有限受众的主题(我明白它们在技术上确实是这样),感觉一点也不顺畅。

我不确定我是否有解决方案,但这每次都困扰着我。

(供参考,谁还记得 Facebook 曾经同时拥有消息和聊天——消息是较早的直接通信形式?然后他们取消了内部邮件式的消息,只保留了即时消息。这很痛苦,当人们在即时消息中写“长篇邮件”时。但我确信那个决定中潜藏着这里的问题:聊天和消息有很多重叠,让它们在一个空间中共存,并使用户在需要时能被吸引到正确的那个空间是很复杂的。即时消息和电子邮件仍然存在并且都在使用,这对我来说证明了拥有两种通信模式是合理的。但在同一个平台上,这就很棘手了。)

1 个赞

你使用的是什么主题?我从侧边栏可以轻松访问所有内容。(我意识到这并不能解决你更广泛的认知失调。)

1 个赞

没有什么要补充的,只是关于聊天/帖子区别的讨论:

以及来自 :discourse:团队的有价值的引述:

2022年,

2024年,

5 个赞

是的,这仍然是一个棘手的问题,是吧?我总是看到用户对该用哪个感到困惑,并且找不到东西。它们是很好的工具,正如 @HAWK 所说,它们各自服务于非常不同的目的。

我怀疑“消息”(Messages)的出现是为了作为一个易于附加的伪消息系统。既然我们有了真正的消息(proper messages),也许是时候继续前进了?

转向语用学,我相信 @stephtara 在上面清晰阐述的这种孤立存在的固有弊端可以通过以下两种方法之一得到显著缓解:

默认情况下,搜索范围扩大到涵盖主题(Topics)、消息(Messages)和聊天(Chat)

我们目前可以通过在搜索中附加 in:all 来涵盖主题和消息(但这不能设为默认设置)。我们目前也可以搜索聊天,但只能在聊天孤岛内搜索。

在我看来,这似乎是可行的——该功能已经存在(尤其是对于主题/消息)。

将“消息”(Messages)改为“私人主题”(Private Topics)

消息本质上已经是私人主题了,只有一些细微的差别——以及不同的主题列表用户界面(如果算上通过 /group 页面的群组消息,则实际上有两个)。

如果我们“全力以赴”,停止将它们标记为“消息”(Messages),并将聊天(我们已经称之为“私信”(DM’s))作为真正的消息,那我们才算真正有进展了。

2 个赞

就我所见,Discord 上的用户也表达了类似但不同的看法——他们忘记了私信(DM)这个功能,或者他们根本不查看私信(尽管有提示)。

对我来说,作为一个事物的保管者和一个网站管理员,如果你愿意这么说,一个有保留的人,最大的显著区别在于保留期:聊天默认是短暂的,只持续 90 天。对我自己和我的论坛来说,我禁用了聊天,并且不使用它。

任何开始或加入新论坛的人,可能都想考虑聊天是否在他们的思维模型中占有一席之地。

我不太了解 Facebook 的用户体验,但我认为我可以这么说,Messenger 被剥离成一个独立的应用程序,人们使用它并将其视为一个独立的空间。这与将私信和聊天合并到一个空间中的想法是相反的。

1 个赞

我使用的是 Meta 上的 Horizon 主题。你说得对,它也在侧边栏里!我想我把侧边栏“弄盲了”(除了分类),因为在我自己的网站上,我把它隐藏了(目前)并移到了头像旁边的汉堡菜单里,试图让界面对我的成员来说不那么杂乱(去哪里找东西的地方太多了)。

也许我需要换一种方式思考,从“所有侧边栏”的角度来考虑。我会花点时间琢磨一下!

1 个赞

感谢您在此收集这些信息!

我认为这可能与普通大众的假设相悖,因为在一个我们都有多年 WhatsApp 聊天记录可以出于任何原因深入了解的世界里。我认为“消息”(Messages)和“聊天”(Chat)自然地对应于电子邮件和即时消息,但有一个区别:您可以邀请某人加入“消息”对话,他们会自动访问整个历史记录,这与电子邮件不同,在电子邮件中,只有当他们被抄送到最后一封电子邮件的底部时,他们才能访问历史记录,而且聊天记录会丢失。

这是真的,越来越多地是这样。但历史记录得以保留。而且 Facebook 已经尝试将某种形式的聊天重新整合到群组中,以频道的形式。在我的社区中,我们非常依赖 Messenger 上的群组讨论,用于版主工作或关于如何管理群组中这个或那个情况的实时讨论。因此,我们也非常依赖聊天记录来回忆就某个案例做出的决定,或者一个麻烦的用户过去是否制造过麻烦。我意识到这与 Discourse 为我们提供的所有出色的版主工具(用户笔记等)相比是无关紧要的。但我确实面对的是习惯于即时消息的用户群体,我有点担心关闭它(尽管非常想关闭)。

唯一缺少的是像当前消息那样的全页显示能力,以及格式化。我们能否拥有两者的优点呢?

我并不太使用 WhatsApp,除了作为一种转瞬即逝的聊天应用。我可能没有理解这里的细微差别。

我同意,我仍然觉得即时消息是短暂的,用于与人们进行快速讨论。我们在哪里意见不一致?

It might be regarding the fact that synchronous and highly interactive communication does not necessarily imply that one won’t want to refer to it later.

Not directly in response to what you say here, but continuing my thoughts on this topic:

  • Chat has the least friction, so that is where people tend to turn to by default. For me, it’s the same mechanics as what caused a lot of conversations to migrate from blogs and their comments to the socials (I unpack this in this post of mine, under “A way to look at interaction”)
  • My experience on Facebook is that people easily get “stuck” in chat (because it’s ongoing, interactive, immediate) and that draws them away from the slower interaction in the group/community
  • Chat is super useful to deal with a crisis or to have a real-time, live exchange on a topic where being able to adjust to feedback instantly is helpful (“let’s drop the e-mail thread and pick up the phone for this”)
  • Messages are wonderful because they are a way to write something more longform (internal e-mail) to somebody, that they will read and respond to when available. In the absence of such a functionality, people “hijack” chat for that, and send “letters” through a communication channel that is made primarily for live, interactive communication (though of course it has flexibility and can also be used asynchronously). This is what happens on Facebook, or Whatsapp: every now and again you receive a message pages long, that you can’t read now, even less respond to now, but the fact it happens in the “instant messaging/chat” channel creates pressure.
  • Both channels (Messages and Chat) have their uses, stemming from what makes them similar (in the case I was bringing up: I’m having “a conversation with this person” – or people) and what makes them different.
  • Guiding people to one or the other is an interface issue as I see things, and not an education one.
  • I don’t see the duration of history retention as a direct consequence of the differences in use cases between the two: it could be used as a tool to try and “prevent” people from overusing chat for important exchanges that shouldn’t be lost, but for me that is relying on education to solve the issue of “getting people to use the right channel for the right things”
  • How do the socials design their interface to control the length of utterances/degree of interactivity on their platforms? The box for writing something on Facebook is small, so people think small. You can’t use formatting. Twitter limited length. On the other side, we have (had? who is still on?) chat spaces like IRC: just a line to write on, and a very visible collective conversation that has a certain speed. Blogging? A new post on WordPress gives me a nearly full-page space to write, with a title!

For me, this is where affordance comes in. Make people “not want” to type in paragraphs in chat, and “want” to move to chat if they’re messaging back-and-forth synchronously. (etc.)

So, aside from thinking things and pointing out what doesn’t “feel” right to me, do I have concrete suggestions? I’m honestly not sure at this stage. Let me try thinking out loud. (I thank you all again for your patience with my sometimes verbose musings.)

My concrete problem as community manager is the following: I would like to keep both chat and messages, because I think I have use cases for both. I also don’t want my community members to get sucked up in chats (or private messages for that matter), because the nature of a support community, particularly where we are dealing with lives (even if they’re “just” cat lives), is that support given in public is more likely to be subject to checks and balances and less likely to go off the rails and have serious consequences. And because I know from experience that when members are chatting away in the background, it satisfies their need for action and connection that doesn’t benefit the larger community. (OK this is drifting out of UX I think, sorry about that.)

So, I’d like to be able to have specific control about who has private message and chat privileges. I don’t want to let normal members chat with each other, but I want staff or certain groups to be able to initiate chat with members if needed. I’d like channels to be accessible on certain conditions.

Just a note: I know Discourse already does a large part of what I’m talking about in this post – I’m just trying to think using my needs as a starting point.

Same with personal messages. But maybe not the same settings. I might want people to be able to exchange personal messages but not chat. Or vice-versa.

Which brings us back to the initial question: say I have access to chat and personal messages, where do I find them and what is going to invite me to use one rather than another? For now, user cards clearly invite me to message. But right next to my avatar is a little chat bubble. So we have two different “entry points” for 1-1 communication (if we stick with that scenario). Either I “see” somebody I want to connect with directly, and I’ll send them a message. Or I think of something to say to someone, and I’m more likely to click on the chat bubble to write to them. Plus, the chat bubble overlays the chat window to what I’m currently doing instead of replacing it.

Whereas if I were to go to “My Messages” in the sidebar, I actually end up in a space that seems to be all about me: my activity, my notifications, my profile. Messages almost seem like an afterthought.

I have the feeling the way things are set up now sends some kind of “mixed message” (no pun intended) regarding how to talk to people.

So, how about grouping messages and chats in some way? Not merging, because as mentioned more than once in this conversation, they have different uses, but they also are cousins (hence my confusion when looking for something that I recall being in one or the other). I’m not sure what label would cover “Messages and Chats” well, but for me it would make sense, if I have had chats with “Rose” as well as message exchanges with her, to have a way to access them easily (metaphorically) side-by-side. I see this as a kind of “My Communication Hub” where I would see who I’ve had personal communications with (individuals or groups) and be able to access them without having to first know if it was through chat or Messages. Because my brain (and I don’t think it’s unique to me) is probably going to know who it was with before knowing if it was chat or messages. Maybe a first step in that direction would be to make the existence of a chat with somebody visible in the message view, and vice-versa.

This would definitely be helpful.

This idea I’m very ambivalent about. I feel the whole concept of “private topics” not intuitive at all. Just like, as mentioned elsewhere, the fact that these “private messages” are not private at all because either party can unilaterally expand the audience without consent of the other party, including for past exchanges.

I really like the way these messages/private topics work, however. But when it comes to labelling, they feel more like “internal e-mail” or the “direct messages” one might have encountered on message boards over the last decades.

But on second thought: sure, why not. We’d have chat (instant messaging) on one side, and private topics (but then make them properly private… I recall a discussion about “personal” instead of “private” for to my ears at least, it’s same-same – you get a letter in the post marked “personal”, that clearly implies it’s not for others). And maybe that could be grouped under Messaging.

And maybe there would be a way to “jump” from one to another (is that a “bad good idea?”, to start in chat and say “make this a topic”, or be in a topic and say “make a chat from this”? Probably a step too far, though I’m seeing this need to drift from one to the other in quite a few posts in this topic, for example:

It could be an invitation: if a topic is morphing into a near-synchronous exchange of short messages, the system could “invite to chat”, or if somebody is typing a three-page letter into the chat input field, invite to “make this a topic instead? you’ll be able to format!”?

Trying to summarize:

  • as I see it both “direct messages/topics” and chat deserve to exist
  • it would make sense to bring them closer “geographically”, for example under a “messages” or “direct communication” heading, which de-silos a bit and presents them more as what they are, two flavours of non-public communication
  • expanding search to chat would be great (isn’t that already possible?)
  • granular access rights for both chats and messages
  • solution to the “private/personal topics that aren’t that personal”?
  • how do we invite people to communicate? (what’s on the user card, what’s highly visible on the interface)

I’m sure a lot of this has been discussed and thought through before and that there are probably solutions to some of my issues that I don’t know of.

2 个赞