1. IM 1.1 互操作性 1.2 尝试开放标准 1.3 主流即时通讯软体 1.4 即时通讯协议比较 1.5 协议支持 1.6 连接性 Connectivity 2. 活跃用户过亿的虚拟社区列表 3. 更多相关连接
1. IM
即时通讯 Instant messaging ( IM ) 技术是一种基于计算机的同步通信技术,允许两方或多方通过互联网或其他计算机网络即时(实时)传输消息。
即时通讯应用和服务, 也称为
“社交信使”social messengers;
“消息应用”messaging apps;
“聊天应用”chat apps;
“聊天客户端”chat clients.
最初仅涉及简单的文本消息交换,如今往往还具备多媒体交换、emojis 表情符号、文件传输、VoIP(语音通话)和视频聊天功能。
1.1 互操作性
大多数即时通讯协议都是专有的,并非设计为可与其他协议互操作,这意味着许多即时通讯网络不兼容,用户无法联系到其他网络上的用户。
截至 2024年,即时通讯服务的碎片化意味着普通用户可能需要使用比以往更多的网络,包括需要下载应用程序和注册,才能与所有联系人保持联系。
多协议客户端可以使用任何即时通讯协议,只需为每个协议添加额外的本地库即可。
多协议即时通讯软件的例子包括 Pidgin 和 Trillian,以及最近的 Beeper。
这些第三方客户端常常因为专有协议的限制而无法跟上时代的步伐,最终被封锁。
例如,2015 年,WhatsApp 开始封禁使用非官方客户端的用户。
主要的即时通讯提供商通常会将正式协议的必要性和安全问题作为做出变更的理由。
1.2 尝试开放标准
过去曾有多次尝试创建即时通讯的统一标准,包括:
- IETF的会话发起协议 Session Initiation Protocol (SIP) 和
- 用于即时消息和状态利用扩展的 SIP (SIMPLE) SIP for Instant Messaging and Presence Leveraging Extensions
- 应用程序交换 Application Exchange (APEX),
- 即时消息和存在协议 Instant Messaging and Presence Protocol (IMPP),
- 基于XML的可扩展消息和存在协议 Extensible Messaging and Presence Protocol (XMPP) ,以及
- 开放移动联盟的即时消息和在线状态服务 Instant Messaging and Presence Service (IMPS),专为移动设备开发。
https://en.wikipedia.org/wiki/Instant_Messaging_and_Presence_Protocol
1.3 主流即时通讯软体
IM | 主要应用国家地区 | 用户数 | 企业 | 国家 | GFW | 部分限制或全部封禁 | IM | |
主流 即时 通讯 软件 |
南美、西欧、非洲、中东、南亚和东南亚 | 20亿 | meta | 美国 | 2017 | cn, 土耳其, 巴西 | ||
北美、北欧、部分中欧国家和大洋洲 | 13亿 | meta | 美国 | 2008 | cn, 俄罗斯, 伊朗, 塔吉克斯坦, 所罗门群岛, | |||
Viber | 中欧和东欧(保加利亚、希腊、塞尔维亚、乌克兰、俄罗斯)市场表现强劲. 菲律宾和越南也取得了一定的成功 |
2.6亿 | 乐天 | 日本 | 2014 | cn, 俄罗斯 | Viber | |
Line | 日本, 台湾, 泰国 | 4亿 | 韩日 | 2014 | cn, 俄罗斯 | Line | ||
Signal | 1亿 | 开源 | 美国 | 2021 | cn, 俄罗斯, 伊朗, 埃及, | Signal | ||
Telegram | 东欧多个国家, 西欧、中东、南亚、东南亚、非洲、中美洲和南美洲多个国家 | 7亿 | 客户端 开源 |
俄罗斯 | cn, 伊朗, 巴西, 巴基斯坦 | Telegram | ||
Skype | 3亿 | 美国 | 2005 | cn, | Skype | |||
Discord | 基于主题的频道和基于云的存储 | 2018 | cn, | Discord | ||||
地区 专用 |
中国 | 12亿 | 中国 | |||||
中国 | 12亿 | 腾讯 | 中国 | |||||
KakaoTalk | 韩国 | 韩国 | 2014 | cn, | KakaoTalk | |||
Zalo | 越南 | 越南 | Zalo |
1.4 即时通讯协议比较
Protocol | Creator | First public release date | License | Identity ( Not inc. alias) |
AsynchroNous message relaying | Transport Layer Security | End-to-end encryption | Unlimited number of contacts | Bulletins to all contacts | One-to-many routing | Spam protection | Group, channel or conference support | Audio/VoIP support | Webcam/Video | Batch file sharing | Media synchronization | Serverless | Binary format | Protocol |
协议 | 创建者 | 首次公开发布日期 | 许可证 | 身份(不含别名) | 异步消息中继 | 传输层安全性 | 端到端加密 | 无限数量的联系人 | 向所有联系人发布公告 | 一对多路由 | 垃圾邮件防护 | 群组、频道或会议支持 | 音频/VoIP 支持 | 网络摄像头/视频 | 批量文件共享 | 媒体同步 | 无服务器 | 二进制格式 | 协议 |
3GPP standards | Friedhelm Hillebrand | 1985 | Proprietary | Phone number (e.g. +15550123) | Yes | No | No | About 250 contacts in SIM, unlimited from phone. | No | serial messages | Medium | No | Yes | 3G-324M/ViLTE | RCS | No | ? | ? | 3GPP standards |
Bitmessage | Jonathan Warren | 2012 Nov | Open standard | Alphanumeric address | Yes | Yes | Yes | Yes | No | Yes | Yes (through proof-of-work) | Yes | No | No | Yes | No | Yes | ? | Bitmessage |
Bonjour | Apple Inc. | 2002 August | Proprietary Freeware; portions under the Apache license | Username | No | No | No | Yes | No | multicast | Medium | No | No | No | Yes | No | Yes | ? | Bonjour |
Briar | Briarproject.org | 2018 May 9 | Open standard | Public & Private key (via QR Codes) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No | No | Yes | ? | Briar |
Discord | Discord Inc. | 2015 May 13 | Proprietary | Discord ID[1] | Yes | No | No | No | No | ? | Medium | ? | Yes | Yes | Yes | ? | No | ? | Discord |
dm3 | corpus.io / dm3.network | 2022 | Open Source (BSD) | ENS (Ethereum Name Service) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No | Yes | Yes | ? | dm3 |
Echo | spot-on.sf.net / goldbug.sf.net | 2013 | Open standard | Key | Yes | Optional | Yes | Yes | Yes | Yes | Yes | Yes | No | No | Yes | Yes | Yes | ? | Echo |
Gadu-Gadu | GG Network | 2000 Jul 17 | Proprietary | UIN e.g. 12345678 |
Yes | Yes | No | Yes | No | Centralistic | Yes (simple) | Yes | Yes | Yes | Yes | No | No | ? | Gadu-Gadu |
IRC | Jarkko Oikarinen | 1988 Aug | Open standard | Nickname!Username@hostname (or hostmask) e.g. [email protected][d] |
Yes, via IRCv3 or MemoServ that differs from the main system | Optional | Many implementations which are mostly Non-interoperable with other IRC clients[4][5][6] | No | No | Simplistic multicast | Medium | Yes (everyone, multiple simultaneous, any size) | many implementations which are incompatible with other IRC clients[9][10] | No | Yes | via BNC | Yes, via DCC CHAT | ? | IRC |
Jami (based on DHT and SIP) |
Savoir-faire Linux Inc. | 2002 August | Open Standard | 40-digit address | Yes | Yes | Yes | Yes | No | Yes | Medium | Yes | Yes | Yes | Yes | No | Yes | ? | Jami (based on DHT and SIP) |
Matrix | Matrix.org | 2014 Sep[11][failed verification] | Open standard | @Username:Hostname (MXID) | Yes | Yes, mandatory | Yes, default for private conversations[12] | Yes | Yes | Yes | Yes (using pluggable server-side filtering modules and contact igNoring) | Yes | Yes | Yes | Yes | Yes | No | ? | Matrix |
Mattermost Inc | 2015 October 2 | Open standard | ? | ||||||||||||||||
MSNP (Windows Live Messenger…) | Microsoft | 1999 Jul | Proprietary | Email address (Microsoft account) | Yes | No | No | Only for certified robots | No | Centralistic | Yes | Yes | Yes | Yes | Yes | Yes | No | ? | MSNP (Windows Live Messenger…) |
MTProto (Telegram) | Telegram Messenger LLP | 2013 Aug | Open standard | Phone number (e.g. +15550123), nickname (e.g. @example) | Yes | Yes | No end-to-end encryption for group chats | Yes | No | Yes | Yes, contact blocking | Yes | Yes | Yes | Yes | Yes | No | ? | MTProto (Telegram) |
Mumble | Thorvald Natvig | 1999 Jul | Open standard | Username | Yes | Yes | No | Only for certified robots | No | Centralistic | Yes | Yes | Yes | No | Yes | No | No | ? | Mumble |
LY Corporation | 2011 June 23 | Proprietary | ? | ||||||||||||||||
OSCAR (AIM, ICQ) | AOL | 1997 | Proprietary (Discontinued 15-Dec-2017)[14] | Username, Email Address or UIN e.g. 12345678 |
Yes | Yes (Aim Pro, Aim Lite) | No | No | No | Centralistic | client-based | Yes (Multiple, simultaneous) | Yes | Yes | Yes | No | No | ? | OSCAR (AIM, ICQ) |
Revolt | Revolt | 2021 | AGPLv3 | Username and discriminator (e.g. MysticPixie#7495)[15] | Yes | Yes | No | Yes | Yes | No | Yes | No | ? | Revolt | |||||
RVP (Windows Messenger, etc.) | Microsoft | 1997 Mar | Proprietary (Discontinued) | Windows Active Directory Login | No | No | ? | No | Centralistic | None | No | ? | ? | No | No | No | ? | RVP (Windows Messenger, etc.) | |
Ricochet | Invisible.im | 2014 Mar | Open standard | Tor onion address | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | No | No | Yes | No | Yes | ? | Ricochet |
Serval Project | Serval Project | 2016 | Open Standard | Digit address | Yes | No | Yes | Yes | Yes | Yes | No | No | Yes | Yes | Yes | Yes | Yes | ? | Serval Project |
Signal Protocol | Signal Foundation | 2014 Feb[16] | Open standard | Phone number (e.g. +15550123) | Yes | Yes | Yes | Yes | ? | Yes | Yes, contact blocking | Yes | Yes | Yes | Yes | Yes | No | ? | Signal Protocol |
SimpleX Messaging Protocol | Evgeny Poberezkin | 2020 | AGPLv3 | No user identifiers | Yes | Yes | Yes | Yes | Yes | Yes, through WebRTC | Yes, through WebRTC | Yes | No | ? | SimpleX Messaging Protocol | ||||
SIP/SIMPLE | IETF | 1996 | Open standard | user@hostname | Yes | Yes | Optional | Yes | Yes | No | Medium | ? | Yes | Yes | Yes | No | Depends on implementation | ? | SIP/SIMPLE |
Skype | Skype | 2003 Aug | Proprietary | Username | Yes | Proprietary | No | No | No | Centralistic | client-based | Yes | Yes | Yes | Yes | No | No | ? | Skype |
Steam Friends | Valve | 2003 Sep 12 | Proprietary | SteamID/Username or Unique Number | Yes | Proprietary | ? | No, although rising | Yes | ? | No | Yes | Yes | No | No | No | No | ? | Steam Friends |
TeamSpeak Systems GmbH | 2001 Aug | Proprietary | Unique ID in base64 | No | No | No | ? | ? | ? | ? | Yes | Yes | No | ? | |||||
TOC2 | AOL | 2005 Sep | Proprietary (Discontinued) | Username or UIN e.g. 12345678 |
Yes | No | No | No | No | Centralistic | No | paying members only | ? | ? | Partial | ? | No | ? | TOC2 |
Threema GmbH | 2012 December | Open standard | ? | ||||||||||||||||
TOX (based on DHT) | irungentoo (GitHub user) | 2013 June | GNU General Public License (GPL) version 3 or later | Public & Private key | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ? | TOX (based on DHT) |
Tuenti | Tuenti | 2006 | Proprietary | Username | Yes | Yes | No | Yes | ? | Yes | Yes | Yes | Yes | Yes | Yes | ? | No | ? | Tuenti |
Tencent | 2011 | Proprietary | Username | Yes | Yes | No | Yes | Yes | Yes | No | Yes | Yes | Yes | No | No | No | ? | ||
Windows Messenger service | Microsoft | 1990 | Proprietary (Discontinued) | NetBIOS | Yes | No | No | Yes | Yes | Yes | No | No | No | No | No | No | No | ? | Windows Messenger service |
XMPP | Jeremie Miller, standardized via IETF | 1999 Jan | Open standard | Jabber ID (JID) e.g. [email protected]/home[f] |
Yes | Yes | Optional | Yes | Yes | Yes | Yes | Yes | Yes, via Jingle | Yes, via Jingle | Yes | Yes | Optional | Yes | XMPP |
YMSG (Yahoo! Messenger) | Yahoo! | 1998, March 9 | Proprietary | Username | Yes | No | No | No | Yes | Centralistic | Yes | Yes | Yes | Yes | Yes | No | No | ? | YMSG (Yahoo! Messenger) |
Zephyr Notification Service | MIT | 1987 | Open standard | Kerberos principal e.g. [email protected] |
Yes | No | No | Yes | Yes | Yes | No | Yes | No | No | No | No | No | ? | Zephyr Notification Service |
协议 | 创建者 | 首次公开发布日期 | 许可证 | 身份(不含别名) | 异步消息中继 | 传输层安全性 | 端到端加密 | 无限数量的联系人 | 向所有联系人发布公告 | 一对多路由 | 垃圾邮件防护 | 群组、频道或会议支持 | 音频/VoIP 支持 | 网络摄像头/视频 | 批量文件共享 | 媒体同步 | 无服务器 | 二进制格式 | 协议 |
1.5 协议支持
摘录协议支持
Name | AIM | ICQ | MSN Messenger |
Yahoo! | IRC | Jabber | Bonjour | Novell GroupWise Messenger |
Lotus Sametime |
Gadu -Gadu |
Skype | 其他 | Name | |
Adium | 1 | 1 | 1 | 1 | 否 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | FaceBookIM Fetion (需安装插件) |
Adium |
Pidgin | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 部分 | 1 | SILC, Zephyr | Pidgin |
Kopete | 1 | 1 | 1 | 1 | 1 | 1 | 否 | 1 | 1 | 1 | 1 | 否 | ? | Kopete |
Miranda IM | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 否 | 1 | 1 | 部分 | 1 | Tlen, LAN, Chat, Xfire, MySpace, IM | Miranda IM |
Trillian Pro | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 否 | 否 | 1 | ? | Trillian Pro |
Centericq | 1 | 1 | 1 | 1 | 1 | 1 | 否 | 否 | 否 | 1 | 否 | 否 | ? | Centericq |
Fire | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 否 | 否 | 否 | 否 | 否 | ? | Fire |
Proteus | 1 | 1 | 1 | 1 | 否 | 1 | 1 | 部分 | 否 | 1 | 否 | 否 | ? | Proteus |
BitlBee | 1 | 1 | 1 | 1 | 否 | 1 | 否 | 否 | 否 | 否 | 否 | 否 | ? | BitlBee |
IM2 | 1 | 1 | 1 | 1 | 1 | 否 | 否 | 否 | 否 | 否 | 否 | ? | ? | IM2 |
Trillian | 1 | 1 | 1 | 1 | 1 | 否 | 否 | 否 | 否 | 否 | 否 | 否 | ? | Trillian |
1.6 连接性 Connectivity
Client | Registration requirement | Independent of mobile phone | End-to-end encryption | Peer-to-peer text chat | Open source servers | Federated servers | Client |
客户端 | 注册要求 | 独立于手机 | 端到端加密 | 点对点文本聊天 | 开源服务器 | 联合服务器 | 客户端 |
Briar | No | Yes | Yes | N/A(P2P) | N/A(P2P) | Briar | |
Discord | Email or Phone | Yes | No | No | No | No | Discord |
Element | No | Yes | Yes | No | Yes | Yes | Element |
Fractal | No | No | Yes | Yes | Fractal | ||
Gadu-Gadu | Email and Phone | No | No | Gadu-Gadu | |||
Gajim | No | Yes | With plugin only | No | Yes | Gajim | |
Gitter | ? | ? | ? | ? | ? | ? | Gitter |
Google Chat | Email; Google account | Yes | Google Chat | ||||
Google Messages (RCS) | Phone | Similar to SMS requirements, RCS messaging requires a valid SIM card to be inserted in the device. RCS chat features may continue to work for up to 14 days, when a SIM card is removed from the device.[106] |
Yes, only for RCS chats | N/A [clarification needed] |
Yes | Google Messages (RCS) | |
ICQ | Phone | Phone required for initial registration. Desktop client can function independently afterwards.[107] |
No | ICQ | |||
Jami | No | No | Yes | Yes | N/A(P2P) | N/A(P2P) | Jami |
Jitsi | No | Yes | No | Yes | Yes | Jitsi | |
KakaoTalk | No | No | No | No | KakaoTalk | ||
Kik Messenger | No | No | No | No | Kik Messenger | ||
Line | Phone | No | No | No | No | Line | |
Linphone | No | Yes | No | No | Yes | Yes | Linphone |
Mattermost | No | Yes | No | Mattermost | |||
Messages (Apple) | Email; Apple ID account | Yes | No | N/A [clarification needed] |
N/A [clarification needed] |
Messages (Apple) | |
Messenger | Email or Phone; Facebook account | Yes | No | No | No | Messenger | |
Movim | No | No | Yes | Yes | Movim | ||
Mumble | No | Yes | Yes | Yes | Mumble | ||
Palringo | No | No | No | Palringo | |||
Paltalk | No | No | Paltalk | ||||
Pidgin | No | Yes | With extension only | Yes | Yes | Yes | Pidgin |
Psi | No | Psi | |||||
RetroShare | Yes | N/A(P2P) | N/A(P2P) | RetroShare | |||
Ricochet | Yes | Yes | N/A(P2P) | N/A(P2P) | Ricochet | ||
Session | No | Yes | Yes | No | Yes | Yes | Session |
Signal | Phone ; iOS or Android device. VoIP | VoIP workaround[110] | Yes | No | Yes | No | Signal |
Skype | Email; Microsoft account | Yes | No | No | No | Skype | |
Slack | Yes | No | No | No | Slack | ||
Snapchat | Email or Phone | No | No | No | No | Snapchat | |
Surespot | No | No | No | Surespot | |||
TeamNote | TeamNote | ||||||
Telegram | Phone ; iOS or Android device | Phone required for initial registration & login. Desktop client can function independently afterwards.[113] |
For some features: secret chats,[114] voice and video calls,[115] and voice chats in groups[115] | No | No | No | Telegram |
Tencent QQ | No | No | No | No | No | Tencent QQ | |
Threema | No | A valid phone number or email address is not required for registration & login. However, the mobile app serves as the primary device, due to the end-to-end encryption architecture.[118] |
Yes | No | No | No | Threema |
Trillian | No | Yes | No | No | Yes | Trillian | |
Viber | Phone | No | No | No | No | Viber | |
Phone or QQ | No | No | No | No | No | ||
Phone | No | Yes | No | No | No | ||
Wire | Email or Phone | Yes | Yes | No | Yes | Yes | Wire |
客户端 | 注册要求 | 独立于手机 | 端到端加密 | 点对点文本聊天 | 开源服务器 | 联合服务器 | 客户端 |
2. 活跃用户过亿的虚拟社区列表
No. | Name | 运营商 | 所在国 | 发布 | 月活跃 | 其他指标 | Name |
1 | Meta Platforms | 美国 | 2004 | 30.70亿 | 21.1亿日活跃 | ||
2 | YouTube | Alphabet Inc. | 美国 | 2005 | 25.04亿 | YouTube | |
3 | Meta Platforms | 美国 | 2009 | 20亿 | 月活跃13亿,日活10亿 | ||
4 | Meta Platforms | 美国 | 2010 | 20亿 | 每日5亿用户 | ||
5 | TikTok | 字节跳动 | 中国 | 2016 | 15.82亿 | TikTok | |
6 | 腾讯 | 中国 | 2011 | 13.43亿 | 微信 | ||
7 | Messenger | Meta Platforms | 美国 | 2011 | 10.1亿 | Messenger | |
8 | Telegram | Telegram | 阿联酋 | 2013 | 10亿 | Telegram | |
9 | Microsoft | 美国 | 2003 | 9.3亿 | 7亿 | ||
10 | Snapchat | Snap Inc. | 美国 | 2011 | 8.5亿 | 4.14亿日活跃用户 | Snapchat |
11 | Douyin | 字节跳动 | 中国 | 2016 | 7.55亿 | 抖音 | Douyin |
12 | Kuaishou | 快手 | 中国 | 2011 | 7亿 | 快手 | Kuaishou |
13 | X (Twitter) | X Corp. | 美国 | 2006 | 6亿 | X (Twitter) | X (Twitter) |
14 | Sina Corporation | 中国 | 2009 | 5.86亿 | 241million daily 新浪微博 | ||
15 | Tencent | 中国 | 1999 | 5.54亿 | 2.67亿日活跃用户 | ||
16 | Qzone | Tencent | 中国 | 2005 | 5.17亿 | Qzone | |
17 | 美国 | 2005 | 5亿 | 1亿日活跃用户 | |||
18 | 美国 | 2009 | 4.98亿 | 9800万美国月活跃用户 | |||
19 | Quora | Quora | 美国 | 2009 | 4亿 | Quora | |
20 | 小红书 | 小红书 | 中国 | 2013 | 3亿 | 小红书 | |
21 | JOSH | VerSe创新 | 印度 | 2020 | 3亿 | JOSH | |
22 | Teams | Microsoft | 美国 | 2017 | 3亿 | 1.45亿日活跃用户 | Teams |
23 | Skype | Microsoft | 美国 | 2003 | 3亿 | 4000万日活跃用户 | Skype |
24 | 百度贴吧 | 百度 | 中国 | 2003 | 3亿 | 1500万注册用户 | 百度贴吧 |
25 | Threads | Meta Platforms | 美国 | 2023 | 3亿 | Threads | |
26 | Viber | Rakuten | 塞浦路斯 | 2010 | 2.6亿 | 1,1690亿注册用户 | Viber |
27 | imo | PageBites | 美国 | 2007 | 2亿 | imo | |
28 | Discord | Discord | 美国 | 2015 | 2亿 | Discord | |
29 | Twitch | Amazon | 美国 | 2011 | 1.8亿 | Twitch | |
30 | Line | Naver | 韩日 | 2011 | 1.78亿 | Line | |
31 | Likee | Bigo Live | 新加坡 | 2017 | 1.5亿 | Likee | |
32 | Picsart | Picsart | 美国 亚美尼亚 |
2011 | 1.5亿 | Picsart | |
33 | Vevo | Vevo | 美国 | 2009 | 1.5亿 | Vevo | |
34 | Tumblr | Automattic | 美国 | 2007 | 1.35亿 | Tumblr | |
35 | VK | VK | 俄罗斯 | 2006 | 1亿 | VK |
3. 更多相关连接
sztom
[email protected]
CC-BY-NC-SA